Visual Studio 2026 v18.11 and its 18.11.1 servicing update add an opt-in setting that stops a solution build as soon as one project fails. Copilot Chat, the Debugger Agent and the Profiler Agent also received major changes. These updates touch everyday .NET 10 and C# 14 work, from compile loops to profiling and Git.
Daniel Marbach draws on his pull requests to the Azure .NET SDK to explain when low-level performance work pays off. He argues that in library code, small allocation decisions multiply across every caller, yet added complexity carries a maintenance cost. The post offers a practical decision framework for library authors and application developers alike.
EF Core 11 RC1 lets you declare indexes on properties nested inside complex types directly in the model. The author checks the resulting PostgreSQL plans with Npgsql and shows where indexing into JSON-mapped data still falls short. A practical read for .NET developers designing data models with complex types.
The Microsoft Intune team used the GitHub Copilot modernization agent to move an enrollment service from .NET Framework 4.7.2 to .NET 8 while hosting it on AKS. The author reports cutting one library's migration from about six weeks to one and a half. The most useful part is the working method: an editable migration plan and progress file kept in the repository, and a clear account of where the agent failed on internal libraries.
Anton Martyniuk's new deep dive maps the caching options in .NET, from IMemoryCache and IDistributedCache with Redis to HybridCache, and explains when each one fits. It stresses that caching should come after fixing slow queries, and shows how a per-process cache can serve stale data once an API runs on several instances. Worth reading before you choose a cache for a scaled ASP.NET Core app.
Reading the request body in logging middleware can leave the endpoint handler and model binding with an empty body. The author reproduces the problem with a 61-byte JSON POST and shows how EnableBuffering plus a position reset fixes it. A pitfall every ASP.NET Core developer who logs payloads should know.
The author explains how traffic spikes and client retries can tip a service over, and why rate limiters and circuit breakers do not fully solve it. Load shedding, which drops requests based on current system health, is presented as the missing piece. The article walks through ASP.NET Core and Kestrel ideas for shedding early and by endpoint priority, useful for anyone running public APIs.
Khalid Abuhakmeh compares every practical way to loop through a List<T> in C#, from foreach and for to List.ForEach, Index() and spans, and benchmarks them on .NET 10 and .NET 11 RC 1. The post also covers safe removal during iteration and async loops. It is a useful reference for choosing the right loop in everyday and hot-path code.
Mitchel Sellers describes how he purged over 18 million historical rows from an S1-tier Azure SQL database by deleting small, committed batches instead of one large statement. The article covers batch sizing, clustered-key range selection, supporting indexes and production monitoring. It is a practical guide for any .NET developer planning a large data cleanup on a shared database.
Jeremy D. Miller explains how to read your own writes in event-sourced systems that use async projections in Marten. Switching from FetchLatest to ProjectLatest removes an extra database round trip by reusing pending events in the session. Wolverine's UpdatedAggregate type then lets HTTP endpoints and message handlers return the current aggregate with less code.
Part 5 of Scott Galloway's series packages the recommendation and intervention ideas from earlier parts into Mostlylucid.Relevance, a framework that runs inside the application process and keeps its state in SQLite. It can serve several isolated domains at once, and an optional native package adds an HNSW vector index. The package also ships an AGENTS.md guide describing extension points and invariants for developers and their coding assistants.
Switching from a regular constructor to a primary constructor can change when fields get their values. The difference matters when a base constructor calls a virtual member. Steven Giesel shows the difference by looking at the code the compiler generates.