.NET Releases

What's new in .NET 11: C# 15, libraries, SDK, ASP.NET Core and EF Core 11

.NET 11 was released on 10 November 2026 as an STS release supported until 14 November 2028. This guide explains the changes most .NET developers will notice: C# 15 union types and closed hierarchies, new library APIs such as Zstandard compression and LINQ FullJoin, a faster SDK, ASP.NET Core 11 and EF Core 11, with links to the official documentation for every item.

.NET 11 at a glance From the source

.NET 11 became generally available on 10 November 2026, during .NET Conf 2026. The first release is 11.0.0. It is an STS (Standard Term Support) release, which now means two years of free support, so it is supported until 14 November 2028, the same day as .NET 10.

On the same day .NET 8 and .NET 9 reached end of support. They no longer get security fixes, so apps still on them should move to .NET 10 or .NET 11.

  • C# 15 is the default language version for projects that target net11.0.
  • F# 11 ships with it, focused on lower compiler memory use and fewer FSharp.Core allocations.
  • Visual Studio 2026 and Visual Studio Code with the C# Dev Kit support .NET 11.
  • .NET 10 remains the current LTS release if you prefer three years of support.

At a glance · Data and databases

11.0

.NET 11 at a glanceC# 15: the language changesRuntime and performanceNew library APIsSDK and toolingASP.NET Core 11EF Core 11Should you upgrade to .NET 11?

C# 15: the language changes From the source

C# 15 brings the biggest change to type design in years: union types and closed hierarchies let the compiler check that a switch expression handles every possible case.

  • Union types: the new union keyword declares a value that is exactly one of several case types, for example a Pet that is a Cat, a Dog or a Bird. A switch over a union must handle every case, so adding a new case shows you every place that needs updating.
  • Closed hierarchies: the closed modifier on a class means only types in the same assembly can derive from it. A switch over a closed base type that handles every direct descendant needs no default branch and gives no warning.
  • Collection expression arguments: a with(...) element at the start of a collection expression passes arguments to the collection's constructor, such as a capacity for a list or StringComparer.OrdinalIgnoreCase for a hash set.
  • Extension indexers: extension blocks, added in C# 14, can now declare indexers, so you can add an index operator to a type you do not own.
  • Labeled break and continue: break and continue can name the label of an enclosing loop, which replaces flag variables and goto when leaving nested loops.
  • Non-virtual static members on interfaces now work on older runtimes that lack default interface implementation support.
  • Memory safety rules are a preview feature: they need the preview language version and a feature flag, and add a safe keyword and an unsafe(expression) form. Do not use them in production code yet.

Runtime and performance From the source

Microsoft describes hundreds of runtime optimizations in .NET 11 and links a detailed performance post from the .NET team.

  • Native AOT apps get faster interface dispatch through a shared dispatch helper.
  • Runtime Async moves the async state machine into the runtime. The documentation says net11.0 projects no longer need EnablePreviewFeatures for it, while the announcement still calls it a preview feature, so test it before relying on it.
  • The minimum hardware requirements for x86, x64 and Arm64 were raised. Check them before upgrading old servers or build agents.
  • .NET MAUI now uses CoreCLR as its default runtime.

New library APIs From the source

  • Zstandard compression in System.IO.Compression, a fast modern alternative to GZip and Brotli.
  • LINQ FullJoin, plus Join and GroupJoin overloads that return tuples. EF Core 11 translates FullJoin to SQL FULL JOIN.
  • New decimal floating-point types Decimal32, Decimal64 and Decimal128.
  • System.Text.Json supports C# and F# union types and can write JSON Lines output.
  • A larger Process API: Process.TryGetProcessById, starting a process suspended with ProcessStartInfo.StartSuspended, sending POSIX signals with Process.Signal, and the ProcessExitStatus type.

SDK and tooling From the source

  • The dotnet CLI now starts through a Native AOT entry point and the MSBuild server is on by default, so everyday commands start faster.
  • dotnet run -e passes environment variables from the command line.
  • dotnet test gains --no-dependencies, --timeout and the DOTNET_TEST_RUNNER environment variable.
  • SDK installers for Linux and macOS are smaller.
  • A new MCP server project template (dotnet new mcpserver) helps you build Model Context Protocol servers for AI agents.

ASP.NET Core 11 From the source

  • Asynchronous validation for forms and APIs, so a validator can await a database or service call.
  • OpenAPI 3.2 is the default document version, with OpenAPI 3.1 still available.
  • Blazor: TempData and session data for static server rendering, URL-based paging and sorting in QuickGrid, a better Virtualize component for items of different heights, server-triggered circuit pause, smaller WebAssembly downloads, and new BasePath, DisplayName and EnvironmentView components.
  • New SignalR features and experimental Blazor AI components.

EF Core 11 From the source

  • Faster queries: EF Core removes unneeded to-one joins, which the team measured as up to 29% faster in a split-query case, and translates GroupBy, MaxByAsync, MinByAsync and FullJoin better.
  • Complex types now work with TPT and TPC inheritance, and you can put keys and indexes on complex type properties.
  • SQL Server: full-text catalogs and indexes in the model, JSON indexes, JSON_CONTAINS and JSON_PATH_EXISTS translations, and experimental vector indexes with VectorSearch.
  • Vector columns are no longer read by default in SELECT, which made some queries many times faster in the team's tests.
  • Breaking change: UseSqlServer now assumes SQL Server compatibility level 160 by default.

Should you upgrade to .NET 11? Analysis

If you are still on .NET 8 or .NET 9, upgrade now: both stopped receiving security fixes on 10 November 2026. The real choice is between .NET 10 and .NET 11, and both are supported until 14 November 2028.

Choose .NET 10 (LTS) if you upgrade every few years, run many services, or depend on libraries that are slow to support new versions. Choose .NET 11 if you want C# 15 union types, the faster CLI and the newest ASP.NET Core and EF Core features, and you are happy to move to .NET 12 when it arrives.

Either way, read the breaking changes list before you start. The ones most likely to matter are correctly rounded Math.Round results, stricter DateOnly and TimeOnly parsing, ZIP and TAR checksum validation, IHost now throwing when a BackgroundService fails, and the new SQL Server compatibility level default in EF Core. Upgrade a small service first, run your tests, and then roll out the rest.

Which .NET versions are still supported? See .NET release dates and end of support for every version.

Sources and further reading

Original: “Announcing .NET 11”, .NET Blog, published 10 Nov 2026, retrieved 14 Nov 2026. This article was generated from the official source using our structured templates and passed automated quality checks. Spotted a mistake? See our corrections policy.