Guide · 9 steps · 22 articles · Reviewed

What's new in .NET 11

.NET 11 was released on November 10, 2026. It is a Standard Term Support release with two years of support, and .NET 10 remains the supported LTS option. This page collects the articles we have featured about the release and puts them in a sensible reading order: the announcement first, then the language, runtime, SDK, web, AI and client changes, and finally the upgrade. Many of these articles were written during the previews, so we note where details may have changed. We will add more as the community publishes on the final release.

Start with the release

The official announcement covers every area of the release, and the documentation overview lists the changes in more detail with a page for each area. Read the support section of the announcement first: .NET 8 and .NET 9 reached end of support on the same day, so if you are on either, your next step is .NET 10 (LTS) or .NET 11.

Announcing .NET 11

.NET Team · .NET BlogIssue 35

.NET 11 is a Standard Term Support release with two years of support, and .NET 8 and .NET 9 reach end of support on the same day, November 10, 2026. Headline changes include C# 15 union types and closed hierarchies, a Native AOT CLI host and warm MSBuild server in the SDK, async validation and OpenAPI 3.2 in ASP.NET Core, and CoreCLR as the default runtime for .NET MAUI. Runtime Async and the Blazor AI components remain preview or experimental.

What's new in .NET 11

learn.microsoft.comIssue 35

The official documentation overview. It lists the changes by area (runtime, libraries, SDK, C# 15) in more detail than the announcement and links to a dedicated page for each, plus ASP.NET Core, EF Core, Windows Forms and WPF. Useful as a reference to search once you know what you are looking for. Check the last-updated line at the top: on release day it still described RC 2.

Learn C# 15

C# 15 is the default language version for projects that target .NET 11. Union types and closed hierarchies let the compiler check that you have handled every possible case. Start with the overview, then read the union types deep dive. Both posts were written during the previews, and the announcement confirms these features no longer need the preview language version. The updated memory safety model is still preview.

Explore new features available in C# 15 preview

Bill Wagner · .NET BlogIssue 28

A tour of C# 15: union types, closed hierarchies, collection expression arguments, extension indexers and labeled break and continue, each with before and after code. Written against Preview 7. The updated unsafe model it describes is still a preview feature that needs an explicit opt-in.

Explore union types in C# 15

Bill Wagner · .NET BlogIssue 22

Explains the union keyword in depth: implicit conversions from each case type, exhaustive switch expressions, null handling, unions with their own members, and how existing libraries can opt in with the Union attribute. Written for Preview 2, so the setup steps at the end (declaring runtime types yourself, the preview language version) reflect that early build.

Runtime and performance

Hundreds of runtime and library optimizations arrive without code changes on your side, though the announcement's own advice is to measure your application. Runtime Async, which moves async suspension into the runtime and gives clearer live call stacks, remains a preview feature that you opt into per project.

Performance Improvements in .NET 11

Stephen Toub · .NET BlogIssue 29

The annual deep dive, with benchmarks and code for each change. Sections cover the JIT (including Runtime Async, bounds checks and vectorization), startup, threading, numerics, strings and spans, collections and LINQ, I/O, networking, JSON, diagnostics and cryptography. It is very long, so use the table of contents to jump to the areas your code depends on.

SDK and libraries

New process APIs, a preview toolchain manager for installing SDKs, and file-based apps that span more than one file. The file-based apps article was written against RC1, where the #:ref directive sat behind an experimental flag. The SDK documentation also describes #:include for splitting an app across files, so check it for the current state of both directives.

Process API Improvements in .NET 11

Adam Sitnik · .NET BlogIssue 24

Described by the author as the biggest update to System.Diagnostics.Process in years. New one-call APIs such as Process.RunAndCaptureText and Process.Run start a process and wait for it, with output capture that avoids deadlocks. Also covers handle inheritance control, KillOnParentExit and a lighter SafeProcessHandle-based API.

Introducing dotnetup: A toolchain manager for .NET

Chet Husk · .NET BlogIssue 31

A public-preview tool that installs and manages user-local SDKs and runtimes on macOS and Linux without administrator access. Stable, preview and daily builds can sit side by side, and dotnetup update refreshes tracked channels while leaving exact-version requirements pinned.

ASP.NET Core and Blazor

How C# unions flow through JSON APIs, validation that can await a database or remote call, and what changed in authentication. The authentication comparison is based on RC2, and Device Bound Session Credentials support is experimental, so verify both against the final release before relying on them.

Use C# unions and closed hierarchies in ASP.NET Core

Dmitrii Korolev · .NET BlogIssue 29

How unions and closed hierarchies behave in Minimal APIs, MVC, SignalR, Blazor and OpenAPI, all through System.Text.Json. Unions serialize as the active case with no discriminator, so cases with the same JSON shape need a classifier. Not supported for route, query, header or form binding. For new contracts you control, the post recommends a closed hierarchy with a discriminator.

Data and EF Core 11

EF Core 11 requires .NET 11, so the two upgrades go together. The first page shows what improved, mostly in how queries become SQL, and the second lists what can break. If you use SQL Server 2019 or older, Entra ID authentication, or the Azure Cosmos DB provider, read the breaking changes before you update packages. Both are official documentation pages that Microsoft keeps updating, so check them again when you upgrade.

What's New in EF Core 11

The official feature list, with code and generated SQL for each change. Highlights: unnecessary joins and ORDER BY columns removed from to-one includes, translation of the new LINQ FullJoin, MaxBy and MinBy, complex types and JSON columns on TPT and TPC inheritance, and migration tooling such as dotnet ef database update --add. SQL Server vector search is marked experimental. The benchmark figures quoted are Microsoft's own scenarios, so measure your queries.

Breaking changes in EF Core 11 (EF11)

Read this before upgrading. For SQL Server: the default compatibility level moves to 160 (SQL Server 2022), so older servers need UseCompatibilityLevel set explicitly, and Microsoft.Data.SqlClient 7.0 moves Entra ID authentication into a separate package. Migrate() now throws when no migrations are found, and split queries throw on concurrent modifications instead of returning empty collections. The Azure Cosmos DB provider has the most changes, including one rated high impact.

AI and agents

The .NET 11 SDK includes an MCP server template (dotnet new mcpserver) built on the official MCP C# SDK, and Blazor gains components for agent user interfaces. The Blazor AI components package is experimental and stays prerelease throughout .NET 11. For a fuller path through this area, see our AI agents and MCP guide.

.NET MAUI on CoreCLR

CoreCLR is now the default runtime for .NET MAUI, which puts mobile apps on the same runtime as the rest of .NET. These posts were written during the previews. Test navigation, custom handlers and trimmed publishing as part of your upgrade, and note that the Microsoft.Maui.Controls.Compatibility package no longer ships.

.NET MAUI Moves to CoreCLR in .NET 11

David Ortinau · .NET BlogIssue 24

CoreCLR replaces Mono as the default runtime for .NET MAUI on Android, iOS and Mac Catalyst, bringing the same runtime and diagnostics tools as server apps. The post is candid that some larger Android apps saw startup or size regressions during the previews, so measure your own app. You can opt back with UseMonoRuntime, and Blazor WebAssembly is not affected.

Plan your upgrade

Update the SDK pinned in global.json, retarget your projects, then review the .NET 11 breaking changes, including the updated minimum CPU requirements. Check your database provider's compatibility as well, using the EF Core step above. These two posts cover Microsoft's AI-assisted tooling for the work: the modernization workflow in GitHub Copilot, and .NET Skills for coding agents.

Step introductions are dotnetdevs.io commentary. Every article belongs to its author; see the full library for everything we have featured.