Editor's note
I kept this issue intentionally mixed: there’s practical performance work, platform guidance, and a few architecture detours. The memory leak piece and the GC pressure article are especially worth a read if you’ve ever chased throughput regressions. I also liked the EF Core Count() vs Any() breakdown and the API testing pipeline write-up for the very different kinds of day-to-day help they offer.
Memory leaks, EF Core, and API tuning
Jasen Fici
May 07, 2025
Midweek is here, and it feels as satisfying as discovering an elegant one-liner solution for a tangled C# conundrum. This Wednesday edition is packed with .NET insights, from the latest framework tricks you didn't know you needed to those architectural debates that mimic the epic battles of your favorite sci-fi sagas. Unleash your inner coding Jedi and propel through our carefully curated selection—because even seasoned developers deserve a touch of midweek magic.
Today's Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Jasen's take on today's picks
Memory Leaks in .NET: From Obvious to Tricky Scenarios
Memory leaks and GC pressure are a good one-two punch for anyone profiling real apps.
10 Hidden Features in .NET 8 You Should Start Using Today
The EF Core Count() vs Any() post is the kind of small optimization that adds up fast.
Deep dive into the upcoming AI-assisted tooling to upgrade .NET apps
I also included tooling and migration pieces because the ecosystem story matters as much as the code.
EF Core under the hood: Count() vs Any()
The DI and Dapper articles make a nice contrast between framework fundamentals and data-access tradeoffs.