.NET 11 brings a substantial round of changes for developers, from new C language features to runtime and tooling improvements. It also arrives just after .NET 8 and .NET 9 reached end of support, making the upgrade question rather less theoretical.
Watch Desk analysis
What happened
Microsoft announced .NET 11 on 11 November, according to Linuxiac. The release introduces C 15, including union types, which let developers represent one of several specified types and can help the compiler catch missing cases in switch expressions. It also adds closed class hierarchies, limiting direct inheritance to the declaring assembly.
Other reported changes include JIT optimisations, improved Native AOT performance, FP16 instruction support on compatible x64 and Arm64 processors, and a Native AOT-based CLI host enabled by default in the SDK. Linux gains in-process crash reporting with managed stack traces and runtime details. Runtime Async, a different approach to asynchronous execution, is available as an opt-in preview rather than a finished default.
For AI developers, the release includes an MCP server project template and experimental Blazor AI components for streaming conversations, tool execution and user approval workflows. Linuxiac also says .NET 8 and .NET 9 reached end of support on 10 November. .NET 11 is a Standard Term Support release with two years of support; .NET 10 remains the long-term-support option.
Why it matters
This is more than a language-version bump: the release touches application performance, command-line tooling, diagnostics and web development. Teams on .NET 8 or 9 should also check their support plans, while those needing a longer support lifecycle may prefer .NET 10 over .NET 11.
The AI additions are worth noting, but they are not the whole story, and some are explicitly experimental. The reported performance improvements are release details, not a substitute for testing workloads that matter to your own applications.
Our read
.NET 11 offers a broad set of practical changes, with C 15 and the tooling improvements among the more immediately legible ones. If you maintain a .NET application, check its current version and support status before choosing a migration target. “Latest” and “best fit for your support needs” are not always the same thing, which is why upgrade plans exist.
What to watch
- How the new language features and runtime changes perform in real workloads.
- When Runtime Async and the Blazor AI components move beyond preview or experimental status.
- Whether teams on .NET 8 and 9 move to .NET 10 LTS or adopt .NET 11’s shorter support cycle.
Discussion spark: Would you choose .NET 11 for its new features, or stay on .NET 10 for long-term support?
Sources and evidence
- Source update (11 November 2026, 23:44 UTC)
Watch Desk is operated by WittyWires as an independent cross-cutting AI news tracker. It does not speak for the organisations or people it covers.