Last week, Microsoft has released .NET 11, the latest version of its development platform, together with C# 15, F# 11, ASP.NET Core 11, .NET MAUI, and Entity Framework Core 11. The release is a Standard Term Support (STS) version and will be supported for two years.
As stated in the announcement, .NET 10 remains the Long-Term Support option, while .NET 8 and .NET 9 reached end of support on the same day, November 10, 2026. The release coincided with this year's .NET Conf, held from November 10 to 13.
C# 15 is the default language version for projects that target .NET 11. It adds union types, declared with the union keyword, and the compiler checks switch expressions over them for exhaustiveness. Closed hierarchies limit derivation to the declaring assembly.
The language also gains collection expression arguments, extension indexers, and labeled break and continue statements, while the memory safety work stays in preview. F# 11, according to the release, lowers compiler memory use and reduces collection allocations in FSharp.Core.
In the SDK, the CLI now starts through a Native AOT host by default and keeps the MSBuild server warm between invocations. The dotnet test command gains run-level timeouts and failure limits, and container publishing can produce reproducible digests. In the runtime, Runtime Async remains a preview and is turned on with a feature flag.
The JIT removes more bounds checks and improves devirtualization. As described in the documentation, the release also raises the minimum hardware requirements, and the x86/x64 baseline moves to x86-64-v2.
The libraries add Zstandard compression to System.IO.Compression, new Process APIs for running a process and capturing its output, and four in-memory stream adapters. System.Text.Json supports C# unions and JSON Lines output, and LINQ gains a FullJoin operator.
ASP.NET Core 11 adds asynchronous validation and generates OpenAPI 3.2 documents by default, which the release notes list as a breaking change. SignalR can refresh authentication without reconnecting.
Blazor receives a CacheView component for static server-side rendering, client-side validation for static SSR forms, and an opt-in automatic circuit pause for inactive tabs. An experimental package with AI components for Blazor is also available.
.NET MAUI now uses CoreCLR as the default runtime, with Mono still available and Native AOT as an opt-in option. As reported, XAML Incremental Hot Reload is on by default for Debug builds, XAML namespace declarations are implicit, and the Microsoft.Maui.Controls.Compatibility package no longer ships.
Entity Framework Core 11 requires .NET 11. It generates fewer unnecessary joins, translates FullJoin, supports complex types and JSON columns with TPT and TPC inheritance, and adds experimental vector search for SQL Server.
Other changes in this release are the dotnet new mcpserver template, the dotnetup toolchain manager in public preview, .NET Skills for coding agents, opt-in modern visual styles in Windows Forms, and reliability fixes in WPF.
On Reddit, the reaction was mixed. Several developers welcomed union types as a replacement for hand-written result classes, and others said that .NET 11 and .NET 10 share the same end-of-support date.
The most upvoted comments argued that AI coding tools have made new releases feel less exciting. Other users criticized the code fix for non-exhaustive switch expressions and asked for the decimal conversion change to be more visible.
For interested readers, the full release notes and the list of breaking changes are available in the official .NET 11 documentation.