.NET 11 Ships With C# 15, Union Types, and an MCP Server Template
Microsoft announced .NET 11 on November 10, with C# 15 union types and closed hierarchies, a Native AOT CLI host, Zstandard compression, and an MCP server template in the SDK. It is the biggest .NET release of the year, and the AI tooling is the tell.

Microsoft announced the release of .NET 11 on November 10, and the headline is not a performance number. It is the language. C# 15 ships with union types and closed hierarchies, two features that change how .NET developers model data, and the SDK now includes an MCP server template, which is Microsoft's way of saying that AI agents are now a first-class thing to build in .NET. The .NET 11 release is the biggest of the year for the platform, and the AI tooling is the part that says the most about where Microsoft thinks development is heading.
The release also lands alongside new SDKs for .NET 8, 9, and 10, so even teams that are not upgrading yet get patches. But the new features belong to .NET 11, and they are worth a look even if you upgrade on a slower schedule.
What the .NET 11 release actually changes
Union types are the feature most developers will feel first. A union type lets a value be one of a fixed set of types, and the compiler checks that you handle every case. If you have ever written a method that returns "either a result or an error" and then relied on discipline to check which one you got, union types turn that discipline into a compiler rule. Closed hierarchies do the same thing for inheritance: they let you declare that a type can only be extended by a known set of subtypes, so the compiler can verify that a switch over those subtypes is exhaustive.
These are not new ideas. Other languages have had them for years, and .NET developers have been asking for them for just as long. Their arrival in C# 15 is a sign that the language is catching up to the way modern code is actually written, where modeling a value as one of several possibilities is more common than modeling it as a class hierarchy.
The Native AOT CLI host is the performance story. Native AOT compiles .NET code ahead of time into a native binary, which starts faster and uses less memory than a just-in-time compiled app. The new CLI host makes that path easier for command-line tools, which is exactly the kind of app where startup time matters most. If you ship a CLI tool in .NET, this is the feature that makes Native AOT worth trying.
Zstandard compression joins the standard library, which is a small addition with a big practical effect. Zstandard compresses better and faster than the formats .NET has shipped by default, and having it built in means developers stop reaching for third-party packages for something this basic.
The MCP server template is the real signal
The most interesting part of the .NET 11 release is the MCP server template in the SDK. The Model Context Protocol is the standard that lets AI agents call tools, read data, and act on behalf of users, and an SDK template means Microsoft expects .NET developers to build MCP servers as routinely as they build web APIs. It is a small thing, a template, but templates are how platforms say "this is normal now."
The timing fits the rest of the month. GitHub Copilot moved into Xcode and JetBrains Air this month, Claude Code got background MCP tasks, and Apache Airflow 3.4.0 added a wider provider for LLM and agent steps. The whole developer tooling world is reorganizing itself around agents, and .NET 11 is Microsoft's entry in that reorganization.
Should you upgrade
If you are on .NET 10, the upgrade path is straightforward, and the C# 15 features are worth it on their own. Union types and closed hierarchies will change how you write new code, and the MCP template gives you a clean starting point for agent tooling. If you are on .NET 8 or 9, the new SDK patches are the priority, and you can plan the .NET 11 move on your own schedule.
One caution: Native AOT still has limits, and not every library works with it. Test your dependencies before committing a production service to the AOT path. And if you build agentic workflows, look at how AWS Step Functions now exposes workflows as tools your agents can call. The pattern is the same everywhere: the workflow is becoming the tool, and the agent is becoming the caller. .NET 11 is built for that world.


