What Is .NET 11? C# 15 Union Types and AI Tooling Explained

.NET 11 is Microsoft’s newest major release of its free, cross-platform developer platform, and it shipped on November 10, 2026. The update adds C# 15 with union types and a faster command-line host built on Native AOT. SDK tooling for building AI agents arrives too. The same release date marks the end of support for .NET 8 and .NET 9. Teams still running either version now face a real decision. Here is what actually changed, and what to check before you upgrade.

What .NET 11 Actually Changes

Microsoft shipped .NET 11 as a Standard Term Support release, not a long-term support version. STS releases get two years of support under the same quality and servicing policy as LTS. That distinction matters. .NET 10 remains available as an LTS option for teams that want a longer runway before their next upgrade. Meanwhile, teams still running .NET 8 or .NET 9 lose official support the same day .NET 11 ships. Microsoft retired both versions on November 10, 2026.

The platform has grown large enough that any version decision touches a lot of code. Microsoft reports more than 7,000 contributors working on .NET. NuGet now hosts over 589,000 unique packages with more than 1.1 trillion cumulative downloads. A release this size rarely breaks everything at once, but it does shift priorities for teams planning their next sprint.

C# 15 Union Types Explained

C# 15 ships as the default language version for projects that target .NET 11. Its headline feature is union types. A union lets a method return one of several declared case types, and the compiler tracks every possibility. For instance, a lookup method might declare public union ProductLookup(Product, ProductNotFound); instead of throwing an exception or returning null.

Callers then handle each case in a switch expression, matching on Product product or ProductNotFound missing. The compiler checks that the code handles every case, a feature Microsoft calls exhaustiveness checking. As a result, a caller cannot forget to handle a missing-product case, unlike with a nullable return type. C# 15 also adds closed class hierarchies, extension indexers, and labeled break and continue statements. Full memory safety work remains in preview.

See also  What Is VS Code Agent Sandboxing? Microsoft's New AI Agent Security Layer Explained

Faster Developer Tools With Native AOT

Startup speed has been a long-standing complaint about the .NET command-line tools, and this release addresses it directly. The SDK now defaults to a Native AOT CLI host for common commands. Simple commands like help and version checks skip the managed runtime entirely. Tool launches benefit the same way, while commands that genuinely need managed execution still use it.

Beyond the CLI host, the MSBuild server now stays warm between invocations by default, cutting repeated build overhead. Linux and macOS installers also shrink through assembly deduplication, though Microsoft has not published exact size figures. These additions resemble other developer productivity tools worth adding to a team’s stack. Engineering leads evaluate tools like this every year, and this one costs nothing beyond an SDK upgrade.

AI Tooling Built Into the SDK

.NET 11 treats AI agent development as a first-class scenario, not an add-on. Running dotnet new mcpserver -o MyMcpServer scaffolds a working Model Context Protocol server. It builds on the official MCP C# SDK, giving teams a head start on exposing tools to AI agents. The Microsoft Extensions for AI libraries add shared interfaces like IChatClient and IEmbeddingGenerator. A project can then swap model providers without rewriting application code.

The Microsoft Agent Framework layers on agents and multi-step workflows. Experimental Blazor AI components let a web app surface chat interfaces directly. Full details live in Microsoft’s .NET 11 announcement, which also covers a new .NET Upgrade canvas built around GitHub Copilot. None of these AI pieces are mandatory. Teams that skip AI entirely still get the C# 15 and performance updates without any extra setup.

See also  What Is Microsoft Copilot Autopilot? Home, Code, and Agent Billing Explained

Migration Tradeoffs and Common Mistakes

The biggest mistake teams make with any STS release is treating it like an LTS one. Because .NET 11 carries only two years of support, teams adopting it now need a migration plan in place. That plan should cover whichever release follows. Teams that prefer stability over new language features often do better staying on .NET 10 until its successor LTS arrives.

Another common trap involves the AI tooling itself. Several pieces, including Blazor AI components and the AG-UI hosting integration, remain explicitly prerelease. Shipping them to production invites breaking changes later. Developers using AI coding assistants for daily development work should treat the new MCP server template the same way. It works well for prototypes, but it is not yet a long-term contract. Finally, .NET MAUI’s switch to CoreCLR as the default runtime changes behavior on platforms that disallow JIT compilation. Mobile teams should test thoroughly before their next release.

Key Takeaways

  • .NET 11 shipped November 10, 2026, as a two-year Standard Term Support release.
  • .NET 8 and .NET 9 reached end of support that same day.
  • C# 15 adds union types with compiler-enforced exhaustiveness checking.
  • The SDK’s CLI host now runs on Native AOT by default for faster commands.
  • A new dotnet new mcpserver template scaffolds AI agent tooling in seconds.

Frequently Asked Questions About .NET 11

Is .NET 11 an LTS or STS Release?

.NET 11 is a Standard Term Support release, which gets two years of support. Microsoft applies the same servicing and quality policies to STS and LTS releases alike.

See also  What Are GitHub Actions Workflow Lockfiles?

Do I Need to Upgrade Immediately if I’m on .NET 9?

Not immediately, but soon. .NET 9 reached end of support on November 10, 2026. It no longer receives security patches, which creates real risk over time.

What Are Union Types in C# 15?

Union types let a method return one of several declared case types instead of throwing exceptions or returning null. The compiler enforces exhaustive handling in switch expressions.

Does .NET 11 Require Rewriting Existing AI Integrations?

No. The Microsoft Extensions for AI interfaces are additive. Existing code that calls model providers directly keeps working without changes.

Is the MCP Server Template Production Ready?

It is a starting point, not a finished product. Treat generated MCP servers as prototypes until you add your own authentication, logging, and error handling.

Will .NET MAUI Apps Behave Differently After This Update?

Possibly. CoreCLR is now the default runtime, and platforms that block JIT compilation fall back to precompiled code and an interpreter. That can change performance characteristics on those platforms.

Final Thoughts

The real decision point in .NET 11 is not C# 15 or the AI tooling. It is the forced migration created by .NET 8 and .NET 9 reaching end of support on release day. Teams on either version should treat this as a deadline, not a suggestion. Everyone else can adopt union types and the faster CLI at their own pace. Check your current version’s support status first, then decide how much of the new AI tooling you actually need.

Photo by Markus Spiske: Pexels

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.