C# Digest
C# Digest
#596 – February 22, 2026
features over technical layer
Vertical slice architecture in .NET
7 minutes by Adrian Balaidor
Code is grouped by feature rather than technical layer, so everything a feature needs lives together. This makes changes easier since you touch one slice instead of many scattered files. Each slice is mostly independent, which reduces the risk of breaking unrelated parts of the app. Teams can work faster because features are self-contained and easier to understand.
Inside the State of .NET 2025: What Modern .NET Engineers Are Actually Using
sponsored by Jetbrains
See what .NET ecosystem (really) looks like – no buzzwords, just numbers. Cross-platform .NET is real, with ~25% for macOS and Linux; ASP․NET Core powers ~60% of apps; Visual Studio and JetBrains Rider now split the IDE market nearly evenly. Discover runtime adoption trends, cloud services distribution, and how AI tools are reshaping workflows. Check out the whole State of .NET 2025 insights.
New runtime async is hitting .NET 11
5 minutes by Steven Giesel
.NET 11 moves async/await handling from compiler-generated state machines into the runtime itself. Local variables can now stay on the stack instead of being promoted to heap fields, reducing memory use and improving speed. Early benchmarks show around 33% faster execution and 42% less memory allocated. Full gains will only appear once core libraries are updated to use the new approach.
Readonly vs immutable vs frozen in C#: Differences and benchmarks
14 minutes by Davide Bellone
Readonly, immutable, and frozen collections in .NET look similar but serve different purposes. Readonly is just a wrapper that blocks changes through one reference, but the underlying data can still change. Immutable collections create true snapshots where any update returns a brand new instance, making them thread-safe by design. Frozen collections, added in .NET 8, are built once at a high cost but offer the fastest lookup performance, making them ideal for static data loaded at startup.
Getting Started with .NET Scheduling in Hangfire
7 minutes by Barret Blake
Hangfire is a .NET library for scheduling and running background tasks. It supports several job types including fire-and-forget, delayed, recurring, and chained tasks. Jobs are stored in SQL Server or Redis, and failed jobs are retried automatically. A built-in dashboard lets you monitor job history and server activity in real time.
Pagination, sorting & searching in ASP.NET Core web API
16 minutes by Mukesh Murugan
Returning all database records in a single API call creates serious performance problems at scale. Adding pagination, sorting, and searching solves this by letting clients request only what they need. In .NET with EF Core, reusable extension methods on IQueryable handle all three cleanly, and the entire chain compiles into one optimized SQL query. For very large datasets, keyset pagination outperforms the standard offset approach by avoiding expensive row skipping.
And the most popular article from the last issue was: