Part of: C#: a working guide for .NET developers, EF Core: a working guide for .NET developers, Performance: a working guide for .NET developers
Editor's note
I put together another intentionally mixed issue today, and the EF Core 10 pair stands out because it covers both cleanup strategy and deployment options in a practical way. I also liked the .NET 10 API versioning post from Microsoft, plus the structured logging piece that reminds teams why readable logs still fail without better shape and context.
EF Core migrations, async bugs, API versioning
Jasen Fici
May 05, 2026
Enjoying the newsletter? Your feedback helps us grow and reach more developers.
Today's Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
Jasen's take on today's picks
Cleaning Migrations in EF Core 10 - Squash, Reset & Manage History
A useful EF Core 10 guide that goes beyond commands and helps teams choose when to squash, reset, or preserve migration history.
A Semantic Kernel Alternative for .NET — When and Why You’d Reach for One
Worth reading if you're evaluating AI plumbing in .NET and want a clearer sense of when Semantic Kernel may be too much or not enough.
Common Async/Await Bug in C# (That Only Shows Up in Production)
Production-only async failures are the ones that hurt most, and this kind of cautionary write-up usually lands better than abstract guidance.
Running Migrations in EF Core 10 - 5 Ways Compared
Good companion to the cleanup article because it compares real migration execution paths instead of pretending there's one correct answer.
🚀 Integrating Hangfire into .NET 9 Applications
A practical Hangfire walkthrough for .NET 9 apps that should help teams add background jobs without treating reliability as an afterthought.
You’re Copying Data in C# Without Knowing It (And It’s Costing You 35% Performance)
Hidden copies are a classic performance tax in C#, so any article that makes them visible is already doing useful work.
How to Collaborate in C#: Cooperative Programming Techniques for Modern .NET Teams
More process-oriented than technical, but coordination patterns matter once a codebase gets large enough to make local decisions expensive.
Getters in C#: The Essential Guide for Modern .NET Developers
Basic on the surface, yet property design details still trip up newer developers and occasionally reveal bad habits in older code too.
LINQ Looks Clean Until You Care About Performance
LINQ ergonomics are wonderful until hot paths say otherwise, and this looks like a timely reminder to measure before assuming.
Your Logs Are Lying to You : Practical Structured Logging for Backend Engineers
Structured logging only pays off when fields, context, and intent are consistent, and this article appears focused on that reality.
Combining API versioning with OpenAPI in .NET 10 applications
Microsoft's post is a solid reference for teams moving to .NET 10 and wanting versioned APIs that stay documented through OpenAPI.
Building a Modern Event-Driven System Locally: .NET 10, Kinesis, and LocalStack
A nice local-first event-driven setup that mixes .NET 10 with Kinesis and LocalStack for architecture experiments without cloud friction.
Your Program Is Living a Lie About Memory
Memory misconceptions cause bad diagnostics, so I appreciate articles that explain the abstraction layers developers routinely forget.