NEWS

.NET 11 arrives with union types in C# 15, Native AOT host in the CLI, and CoreCLR as the default in MAUI

.NET 11 arrives with union types in C# 15, Native AOT host in the CLI, and CoreCLR as the default in MAUI
Image: Redação iMasters
News
Reading
5 min
Tables
1
In short

Released during .NET Conf 2026 week, .NET 11 ships with two years of standard support and changes core pieces of the platform, from the compiler to the MAUI runtime.

Microsoft released .NET 11 during .NET Conf 2026 week, an event held from November 10 to 13. The version arrives alongside C# 15, F# 11, ASP.NET Core 11, an updated .NET MAUI, and Entity Framework Core 11, according to the announcement reported by InfoQ.

Support cycle: who's out, who stays

.NET 11 is an STS (Standard Term Support) release, with two years of support. Those who need long-term stability stay on .NET 10, which remains the family's LTS option. .NET 8 and .NET 9 ended official support on the same day, November 10, 2026, a date that coincided with .NET Conf week.

VersionTypeStatus as of 11/17/2026
.NET 8LTSSupport ended on 11/10/2026
.NET 9STSSupport ended on 11/10/2026
.NET 10LTSActive support
.NET 11STSReleased, 2 years of support

Those running production services on .NET 8 or 9 need to migrate now. The community reaction, according to InfoQ's report, already pointed to a curious detail in Reddit threads: .NET 10 and .NET 11 share the same end-of-support date, which reduces the advantage of waiting for the newer LTS version before migrating.

C# 15 brings union types

The most discussed language change is the arrival of union types, declared with the union keyword. The compiler now checks switch expressions over these types for exhaustiveness, and closed hierarchies limit derivation to the assembly where the type was declared.

In practice, union types replace much of the code that today is written by hand to represent a result that can be of one type or another, such as custom Result<T> classes. This is exactly the point that, according to InfoQ, most excited developers in Reddit discussions about the release.

C# 15 also adds:

  • Collection expression arguments, to pass arguments inside collection expressions;
  • Extension indexers, indexers defined as extension methods;
  • Labeled break and continue, to control nested loops with more precision.

The language's memory safety work remains in preview, with no stabilization date announced. C# 15 becomes the default language version for projects targeting .NET 11.

F# 11 and the rest of the SDK

F# 11 reduces compiler memory usage and decreases collection allocations in FSharp.Core, according to the release notes.

In the CLI, the structural change is the new host: the dotnet command now starts by default through a Native AOT host, and the MSBuild server stays active ("warm") between successive invocations. This tends to reduce startup time for repeated commands in CI pipelines and in day-to-day local work.

Other additions to the SDK:

  • dotnet test gains per-run time limits and failure limits (run-level timeouts and failure limits);
  • Container publishing can generate reproducible digests;
  • dotnet new mcpserver is a new template for MCP servers;
  • dotnetup, a toolchain manager, enters public preview;
  • .NET Skills, aimed at coding agents, becomes part of the ecosystem.

Runtime: AOT, JIT, and hardware requirements

In the runtime, Runtime Async remains in preview and is enabled via a feature flag, not by default. The JIT removes more array bounds checks (bounds checks) and improves call devirtualization.

Microsoft also raised the minimum hardware requirements: the x86/x64 baseline becomes x86-64-v2, which drops support for older processors that don't meet this instruction set.

Libraries, ASP.NET Core, and Blazor

.NET 11 libraries gain Zstandard compression in System.IO.Compression, new Process APIs to run a process and capture its output, and four in-memory stream adapters. System.Text.Json now supports C# union types and JSON Lines output, and LINQ gains the FullJoin operator.

In ASP.NET Core 11, asynchronous validation arrives as a native feature, and OpenAPI 3.2 document generation becomes the default, a change the release notes classify as a breaking change. SignalR can now renew authentication without needing to reconnect the client.

Blazor receives the CacheView component for static server-side rendering, client-side validation for forms in static SSR, and an optional automatic circuit pause for inactive tabs. An experimental package with AI components for Blazor is also available.

MAUI changes the default runtime

The most relevant change for those working with cross-platform apps is that .NET MAUI now uses CoreCLR as the default runtime, with Mono no longer the default option (it remains available). Native AOT remains an opt-in option for those who need shorter startup times and smaller package sizes.

Other changes in MAUI:

  • XAML Incremental Hot Reload comes enabled by default in Debug builds;
  • XAML namespace declarations become implicit;
  • The Microsoft.Maui.Controls.Compatibility package is no longer distributed.

Those maintaining legacy MAUI projects that depend on this compatibility package need to review their migration before updating.

Entity Framework Core 11 requires .NET 11

Entity Framework Core 11 only runs on .NET 11, with no backward compatibility. It generates fewer unnecessary joins, translates the new LINQ FullJoin operator, and supports complex types and JSON columns in TPT and TPC inheritance scenarios. The version also adds experimental vector search for SQL Server.

Mixed reaction in the community

According to InfoQ, the Reddit reaction to the release was mixed. Besides the enthusiasm for union types, the top-voted comments argued that AI coding tools have made the release of new .NET versions less exciting than it used to be.

Other developers criticized the suggested code fix for non-exhaustive switch expressions and asked that the change in decimal conversion behavior be made more visible in the release notes.

For those deciding to migrate, the next step is to check the full list of breaking changes in the official .NET 11 documentation, paying special attention to the raised hardware baseline, the default OpenAPI 3.2 generation, and the removal of the MAUI compatibility package.

Translated from the Brazilian Portuguese original · Read the original