By ByteBot
Microsoft dropped .NET 11 Preview 7 on August 11 — the last major preview before the September RC window closes and the feature set freezes for good. Two changes flip to default behavior and will hit your build pipeline regardless of readiness: the NativeAOT CLI path and the MSBuild server. Everything else is incremental improvement, but these two are worth your attention now.
NativeAOT CLI Is Now the Default
The NativeAOT-based command-handling path, which debuted behind an opt-in flag in Preview 6, now runs by default across all supported platforms — including macOS and Linux, where it was previously gated. The practical result is a 5.5x speedup for dispatching CLI commands. Microsoft’s own benchmark: dotnet tool list drops from 378ms to 68ms.
The scope matters here. NativeAOT handles lightweight dispatch operations — dotnet --version, dotnet --info, tool queries, and external-command resolution. Commands that require MSBuild or NuGet in-process — build, run, test, pack, publish — still use the managed path. So no, your build times are not about to 5x.
But for CI pipelines that chain CLI pre-flight checks, scripts that poll tool versions, or tooling wrappers, the aggregate savings add up. If you hit regressions — edge cases around platform bindings are possible — the escape hatch is setting the environment variable DOTNET_CLI_ENABLEAOT to false.
This is also a philosophical statement. Go’s pitch has always included near-instant native binaries. .NET still can’t match Go’s cold-start times for build commands, but 68ms is a different story from 378ms. The gap is closing.
MSBuild Server Is On by Default
The MSBuild server keeps a warm worker process alive between CLI invocations. Run dotnet build followed by dotnet test, and the second command skips MSBuild startup entirely. For tight local development loops — build, test, fix, repeat — this is a meaningful quality-of-life improvement.
One honest caveat: if your CI runs on ephemeral containers that spin up fresh for each step, the MSBuild server process dies between steps and you get none of the benefit. Persistent agents gain. Ephemeral containers stay as-is.
Async Methods Finally Get the JIT Treatment
This one flew under the radar in most coverage. Async methods have always bypassed the tiered JIT compilation pipeline — they ran perpetually at tier0, optimized for compilation speed rather than steady-state throughput. Preview 7 fixes that. Async methods now flow through tiering like every other method.
If your app is async-heavy — web APIs, message consumers, background services — you may see genuine runtime performance improvements without touching a line of code. The kind of change that’s easy to miss but shows up in load tests.
C# 15: Labeled Break, Union Patterns, and Better Exhaustiveness
Three C# 15 language features arrive in Preview 7. The most immediately useful is labeled break and continue. You can now name an enclosing loop or switch and break or continue it directly from an inner construct — no flag variable, no goto:
outerLoop: foreach (var outer in outerList)
{
foreach (var inner in innerList)
{
if (inner.Matches(outer))
break outerLoop;
}
}Discriminated union fans get two improvements: union patterns now use a try-both approach — the compiler tests the pattern against the union itself first, then against its contained value — and switch-expression exhaustiveness now correctly handles generic parameters constrained to a closed type. Both reduce the boilerplate and false compiler warnings that have made union types cumbersome in earlier previews.
Blazor: Circuits That Know When You Leave
Two Blazor changes deserve attention. Interactive Server circuits now auto-pause when a browser tab is hidden — after a configurable delay (default: two minutes), the server-side circuit suspends and releases its resources. This is quietly significant for apps with large numbers of concurrent idle users, where connection bloat kills server resources at scale.
The new <CacheView> component caches the rendered output of a server-side subtree. On a cache hit, it replays stored HTML instead of re-executing the render tree. For content-heavy SSR pages with slowly-changing sections, this is a straightforward performance lever worth pulling.
Also in Preview 7
A few library additions worth knowing: System.Net.Http gains GZipCompressedContent, BrotliCompressedContent, and ZstandardCompressedContent wrappers for compressing request bodies without manual setup. System.Numerics adds Decimal32, Decimal64, and Decimal128 — IEEE 754-2019 decimal types for financial and scientific precision work. ZIP archives now support AES password encryption. EF Core’s Cosmos DB provider drops Newtonsoft.Json in favor of System.Text.Json. And dotnet test picks up --timeout and --maximum-failed-tests flags for better CI fail-fast behavior.
Test Now — RC1 Is Three Weeks Away
Preview 7 is the final feature preview. RC1 arrives in September and will be feature-frozen — meaning the defaults, the behaviors, and the breakages visible in Preview 7 are likely what ships in November. If you maintain .NET libraries, CI pipelines, or containerized applications, now is the time to run your test suite against Preview 7 and file issues before RC1 hardens the surface.
.NET 11 GA is scheduled for November 10, 2026. The complete release notes — covering runtime-async improvements, MAUI passkey support, and the full list of breaking changes — are on the official .NET blog. The InfoQ breakdown is useful for a structured overview of each area. And if you want the raw feature list by component, the Microsoft Learn what’s-new page tracks the cumulative .NET 11 changes across all previews.
