Editor's note
I pulled together another intentionally mixed issue, from platform behavior changes to architecture and tooling. The BackgroundService exception fix in .NET 11 is the kind of runtime detail that can quietly change production behavior, and Gérald Barré’s OpenTelemetry context piece is especially useful if you’re tracing work across boundaries. I also liked the practical spread here: rate limiting for busy APIs, Dapper for data access, and a solid vertical slice architecture walkthrough.
Enjoying the newsletter? Your feedback helps us grow and reach more developers.
Today's Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Jasen's take on today's picks
.NET MAUI Community Standup: Rust, SkiaSharp Everywhere, AI/ML Live Processing
A broad MAUI standup with enough crossover ideas to interest Blazor folks too, especially around drawn UI and live AI processing.
Microsoft is tightening restrictions on the use of unsafe code in C# - Techzine Global
I’m cautious here since the source text is thin, but any tightening around unsafe code is worth tracking for low-level libraries.
BackgroundService exceptions now propagate in .NET 11
This is an important runtime fix. Hidden BackgroundService failures have surprised people for years.
ASP.NET Core Rate Limiting Best Practices for High-Traffic APIs
Good operational guidance for API teams that need guardrails before traffic spikes expose weak defaults.
C#: Inheritance vs Composition — When to Use Each and Why AI Can't Decide for You
A sensible design discussion. “Prefer composition” is too shallow unless you also talk tradeoffs and context.
The Interval Is the Thing: Modelling Range Types as First-Class Domain Objects in .NET
Interesting domain modeling piece, especially for teams pairing rich types with PostgreSQL range support.
Zstandard compression in .NET 11
Nice to see Zstandard land in .NET 11. Practical compression options matter more than they sound.
.NET Performance in Cloud: The Silent Killers Nobody Talks About
Cloud performance problems are often death by a thousand cuts, not one dramatic bottleneck.
CLAUDE.md for .NET Developers - Complete Guide with Templates
Useful if your team is standardizing how Claude should understand repo conventions and project memory.
20 Advanced Claude Code Tips for .NET Developers
If you’re already using Claude Code, these are the workflow tips that usually move the needle.
C#: Should This Be a Class, Record, Struct, or Interface?
Another good C# decision framework. Type selection has long-term design consequences.
Remove Nodes That Have a Greater Value on Their Right in a Linked List
More algorithm practice than production engineering, but still a decent walkthrough of an efficient approach.
The complete guide to mastering Dapper micro-ORM in .NET
A handy Dapper refresher for developers who want control over SQL without giving up mapping convenience.
How to Structure Production Apps with Vertical Slice Architecture in .NET in 2026
Vertical slice architecture keeps showing up because it solves real team-scale organization problems.
Why Do Some Developers Build Maintainable Software While Others Keep Fixing Bugs?
Maintainability is less about syntax knowledge and more about habits, boundaries, and discipline.
Dynamic LINQ in Production: How I Built Runtime Query Parsing That Doesn’t Suck
Dynamic LINQ can get messy fast, so production-focused guidance is welcome here.
Propagating OpenTelemetry context in .NET
Context propagation is one of those observability details that separates usable traces from broken ones.
Blazor - How to set a base component for all Razor components
Small Blazor tip, but a valuable one if you want shared component behavior without repetitive boilerplate.
Enhancing Code Reliability in .NET with TreatWarningsAsErrors
Treating warnings as errors is still one of the cheapest quality wins available.
10 Potentially Harmful NuGet Packages (and Why)
Package sprawl is a real risk area. Articles like this are useful when they stay concrete.