.NET 11: What’s New, Release Date and Upgrade Guide
.NET 11 is the newest version of Microsoft’s open-source development platform, released on 10 November 2026. It is a Standard Term Support (STS) release with two years of support, until 14 November 2028. It ships with C# 15, which brings union types to the language, along with a faster runtime and SDK, new ASP.NET Core and Blazor features, and a .NET MAUI release that runs on CoreCLR by default. On the same day, .NET 8 and .NET 9 reached end of support.
This guide covers what changed in .NET 11, how it compares with .NET 10, what the end of support for .NET 8 means for your applications, and how to plan the upgrade.
What Is .NET 11?
.NET 11 is the annual November release of .NET, the cross-platform runtime, libraries, SDK and languages (C#, F#, Visual Basic) used to build web applications, APIs, cloud services, desktop software and mobile apps. Microsoft announced it at the opening of .NET Conf 2026 and published the SDK and runtime the same day.
Odd-numbered versions of .NET are STS releases, and even-numbered versions are Long Term Support (LTS) releases. Since .NET 9, Microsoft supports STS releases for 24 months instead of 18, so .NET 11 and .NET 10 now reach end of support on the same date. That changes the old rule of thumb that production systems should stay on LTS versions only.
To use it you need the new SDK and an up-to-date Visual Studio 2026, or Visual Studio Code with the C# Dev Kit. Installing the SDK alone does not move a project to the new version: you retarget it by setting net11.0 as the target framework.
.NET 11 Release Date and Support Timeline
The .NET 11 release date was 10 November 2026, after three release candidates, starting with RC1 on 8 September 2026, which already carried a go-live license for production use. The table shows where each current version stands, according to the official .NET support policy.
| Version | Release type | Released | End of support |
|---|---|---|---|
| .NET 11 | STS | 10 November 2026 | 14 November 2028 |
| .NET 10 | LTS | 11 November 2025 | 14 November 2028 |
| .NET 9 | STS | 12 November 2024 | Ended 10 November 2026 |
| .NET 8 | LTS | 14 November 2023 | Ended 10 November 2026 |
The .NET release schedule is predictable: a new major version every November, with monthly patch releases on Patch Tuesday. The next LTS release, .NET 12, is expected in November 2027. If you want to compare LTS vs STS for your own roadmap, the practical difference today is only which version you will move to next, since .NET 10 and .NET 11 share the same end date.
What’s New in .NET 11: Key Features at a Glance
The table summarises the changes that matter most for teams planning work in 2027. The sections below explain each area.
| Area | Main changes |
|---|---|
| C# 15 | Union types, closed hierarchies, collection expression arguments, extension indexers, labeled break and continue |
| Runtime | JIT devirtualization and bounds-check elimination, Runtime Async (preview), in-process crash reports, new hardware baseline |
| SDK and tooling | Native AOT-compiled CLI host, MSBuild server on by default, smaller Linux and macOS installers, faster dotnet format |
| Libraries | Union and JSON Lines support in System.Text.Json, new stream types, an expanded Process API |
| ASP.NET Core and Blazor | TempData and session for static server rendering, asynchronous form validation, improved Virtualize and QuickGrid |
| .NET MAUI 11 | CoreCLR as the default runtime, compatibility package removed, Android API 24 minimum |
| Data and AI | EF Core 11 with full joins and SQL Server vector search, Microsoft.Extensions.AI, an MCP server template |
For the full list of new features, see Microsoft’s What’s new in .NET 11 overview.
C# 15: Union Types and Other Language Changes
C# 15 is the default language version for projects that target net11.0, and its headline feature is the one C# developers have requested for years: C# 15 unions. A union type holds a value of exactly one of several case types, and the compiler knows the full list of cases:
public record class Cat(string Name);
public record class Dog(string Name);
public record class Bird(string Name);
public union Pet(Cat, Dog, Bird);
Each case type converts to Pet implicitly, and a switch expression over a Pet is exhaustive: if you add a new case later, the compiler flags every place that does not handle it. For business software, this replaces a lot of hand-written result and state classes with something the compiler checks for you. System.Text.Json can serialize unions too.
The other language features are smaller but useful in daily work:
- Closed hierarchies. A
closedclass or record can only be derived from inside its own assembly, so aswitchover it can be exhaustive without adefaultbranch. - Collection expression arguments. A leading
with(...)passes constructor arguments, for example a capacity, to the collection being created. - Extension indexers. Indexers can now be declared in
extensionblocks, next to extension methods and properties. - Labeled
breakandcontinue. You can exit or continue an outer loop directly from a nested one. - Static interface members on older runtimes. Non-virtual static interface members now compile for older target frameworks as well.
New memory-safety rules, which let code use pointers without an unsafe block in more cases, are still in preview and need an explicit opt-in. Everything else in the list works without LangVersion preview settings.
Runtime and Performance Improvements
Every .NET release makes existing code faster without changes, and .NET 11 performance work continues that pattern. Microsoft describes hundreds of runtime optimizations in this release. Two examples from its micro-benchmarks: formatting a nullable integer went from 9.583 ns to 1.987 ns with no allocation, and a generic virtual method call that the JIT can now devirtualize went from 6.678 ns to 1.764 ns. These are small operations, but they run millions of times in a busy API.
Other runtime changes worth knowing about:
- Runtime Async (preview). The runtime itself can now handle
asyncmethods instead of relying only on compiler-generated state machines. In Microsoft’s example, a stack trace shrinks from 13 frames to 5. It is opt-in for now and not yet recommended for production. - Crash reports. Linux, macOS and mobile apps can write in-process crash reports, which makes production failures easier to diagnose.
- ReadyToRun gains. Precompiled code for
Comparer<T>.DefaultandEqualityComparer<T>.Defaultis up to 20 times faster. - New hardware baseline. On x86 and x64, .NET 11 requires CPUs that support the
x86-64-v2instruction set. Older servers and virtual machines that lack it will not start these applications, so check your hosting before you upgrade.
The SDK got faster as well. The dotnet command-line host is now compiled with Native AOT, which removes 600–700 ms of startup on every command, and the MSBuild server is on by default. On Linux, the x64 SDK tarball shrank from 230 MB to 189 MB, and in Microsoft’s monorepo test dotnet format for a single file dropped from 1.09 s to 0.55 s. Faster local builds and smaller CI images are a direct saving for teams that build many times a day.
ASP.NET Core and Blazor in .NET 11
For web teams, Blazor .NET 11 changes focus on static server-side rendering (SSR), the mode where pages render on the server without a live connection. Pages in this mode can now read and write TempData and session values through new parameter attributes, which covers redirect-after-post messages and multi-step forms without making the page interactive. ASP.NET Core also adds asynchronous form validation, so a form can check, for example, whether a username is already taken before it submits.
Other Blazor additions include a DisplayName component that reads [Display] attributes, a Virtualize component that no longer assumes all items have the same height, QuickGrid paging and sorting stored in the URL (so a filtered view can be bookmarked or shared), and server-triggered pausing of Blazor Server circuits. The new Blazor AI components are experimental and stay in preview throughout this release.
If you are still on the Blazor model introduced in .NET 8, our overview of the .NET 8 Blazor changes explains render modes, the foundation that .NET 9, 10 and 11 build on.
.NET MAUI 11: CoreCLR by Default
The biggest platform change in .NET 11 MAUI support is the runtime: .NET MAUI 11 uses CoreCLR, the same runtime that powers server applications, as the default runtime on all its platforms. Until now, Android and iOS apps ran on the Mono runtime. A single runtime across mobile, desktop and server means the same behavior, diagnostics and performance work everywhere. Native AOT remains an opt-in publish option, and Native AOT for Android is experimental.
Other changes that affect existing apps:
- The
Microsoft.Maui.Controls.Compatibilitypackage is no longer shipped, so code that still depends on Xamarin.Forms-era renderers must move to handlers first. - The minimum Android API level rises from 21 to 24, and Android x86 is no longer supported.
- Shell on Android, and navigation and tab pages on iOS and Mac Catalyst, now use the handler architecture by default.
- XAML incremental Hot Reload arrives as a preview feature.
.NET MAUI has its own support policy: MAUI 11 is supported until 9 May 2028, and MAUI 10 until 11 May 2027. New to the framework? Start with our guide What Is .NET MAUI.
Data and AI Building Blocks in .NET 11
EF Core 11 requires .NET 11 and does not run on earlier versions or on .NET Framework, so database access is often the reason a team upgrades. It translates the LINQ FullJoin operator to SQL FULL JOIN, supports complex types and JSON columns with TPT and TPC inheritance, and prunes unneeded joins: Microsoft measured a 29% improvement in a common split-query scenario. On SQL Server it adds vector indexes and a VectorSearch() function for semantic search, which SQL Server itself still labels experimental.
For AI features, the base layer is Microsoft.Extensions.AI, a set of shared abstractions such as IChatClient and IEmbeddingGenerator that let you switch model providers without rewriting application code. The new SDK adds a dotnet new mcpserver template built on the official Model Context Protocol C# SDK, so a .NET service can expose tools to AI agents, and works with the Microsoft Agent Framework for multi-agent workflows. Parts of that stack, such as the AG-UI hosting integration, are still prerelease, so check the status of each package before you build on it.
.NET 10 vs .NET 11: Which Version Should You Choose?
With equal end-of-support dates, the .NET 10 vs .NET 11 decision comes down to what you need now and how often you are willing to upgrade.
| Choose | When |
|---|---|
| .NET 11 | You start a new project, want union types or the latest Blazor and EF Core features, build mobile apps with .NET MAUI, or need the newest runtime and SDK performance. |
| .NET 10 | You are moving a large system off .NET 8, depend on third-party libraries that have not yet released .NET 11 builds, or your hosting cannot meet the new x86-64-v2 hardware baseline. |
Both paths end in November 2028, and the next stop for both is .NET 12 LTS. For most actively developed applications, the newer release is a reasonable target. For systems that change rarely, .NET 10 is the conservative choice with the same support window. Either way, the jump from 10 to 11 is far smaller than the jump from 8 to 10.
.NET 8 and .NET 9 End of Support: What It Means for Your Apps
.NET 8 end of support arrived on 10 November 2026, together with .NET 9 end of support. Since then, Microsoft no longer ships security patches or bug fixes for either version. Your applications keep running, but any vulnerability found from now on will stay open, and Microsoft’s support covers only supported versions.
For many organisations this is also a compliance issue. Security audits, ISO 27001 and SOC 2 assessments and enterprise customers’ vendor questionnaires usually ask whether production software runs on supported platforms. An unsupported runtime becomes a finding in each of them.
If you still run .NET Framework 4.x applications, the picture is different: they follow the Windows support lifecycle, but they cannot use any of the features described above, and migrating them to modern .NET is a separate, larger project.
How to Upgrade to .NET 11: A Practical Plan
Whether you upgrade to .NET 10 or go straight to .NET 11, the steps are the same. A typical plan to migrate .NET 8 to .NET 10 or 11 looks like this:
- Inventory. List every application, service and library, with its target framework, hosting and the NuGet packages it depends on. Check that your key packages support the version you choose.
- Check the infrastructure. Confirm that servers, build agents and container base images support the new runtime, including the
x86-64-v2CPU baseline for .NET 11. - Read the breaking changes. Microsoft publishes a list for each release. This time it includes saturating floating-point conversions, correctly rounded
Math.Roundresults, andIHost.RunAsyncthrowing when a background service fails. - Update the SDK and the projects. Install the new SDK, update
global.json, change the target framework tonet10.0ornet11.0, and update packages. - Use the tooling. The .NET Upgrade Assistant is deprecated. Microsoft now recommends the GitHub Copilot modernization agent, included in Visual Studio 2026 and Visual Studio 2022 17.14.16 or later, which builds a step-by-step plan and commits each change so you can review or roll it back.
- Test and roll out gradually. Run your automated tests, compare performance and memory with the old version, and release service by service rather than all at once.
Diatom Enterprises has built software on .NET since 2007. Our custom .NET development team migrates applications from .NET Framework and older .NET versions, and if your own team needs extra hands for the upgrade, you can hire .NET developers who have done these migrations before. For an earlier step in the platform’s history, see our article on web application development with .NET 9.
FAQ
Is .NET 11 LTS?
No. .NET 11 is a Standard Term Support (STS) release. Because STS releases now get 24 months of support, it is supported until 14 November 2028, the same date as .NET 10 LTS.
When was .NET 11 released?
.NET 11 was released on 10 November 2026, at the start of .NET Conf 2026.
Should I wait for .NET 12 instead of upgrading?
Not if you are on .NET 8 or .NET 9. Both are already out of support, and .NET 12 is not expected until November 2027. Move to .NET 10 or .NET 11 now; the later step to .NET 12 will be small.
Which Visual Studio version supports .NET 11?
Microsoft requires an up-to-date Visual Studio 2026. Visual Studio Code with the C# Dev Kit is also supported.
Do I need to change my code to upgrade to .NET 11?
Usually little. Most applications only need a new target framework and updated packages. Review the breaking changes list and the new hardware baseline, and run your tests before you deploy.
Conclusion
This is a strong release: union types change how you model data, the runtime and SDK are faster without code changes, and .NET MAUI finally runs on the same runtime as the server. Its STS label matters less than before, because it is supported as long as .NET 10. The urgent part is not the new features but the calendar: .NET 8 and .NET 9 are out of support, and every month on them adds risk. Pick your target version, check your dependencies and hosting, and plan the upgrade now.
Table of content
Years in business
Senior engineers
Projects delivered