Most .NET teams have a standing policy: skip the STS release, wait for the LTS. .NET 11 makes that reflex expensive. Union types are finally real in C# 15, Runtime Async cuts memory allocations by several orders of magnitude, and — the part most people are sleeping on — the MCP server template now ships inside the .NET SDK. If your team builds tooling for AI agents, the upgrade clock started November 10.
MCP Server Template, Now In-Box
Until .NET 11, building a C# MCP server meant installing a separate NuGet package and wiring things up yourself. That changes with the mcpserver project template, which is now bundled directly in the SDK. One command:
dotnet new mcpserver -n MyMcpServer
That scaffolds a working MCP server with a Program.cs, a .mcp/server.json configuration file, and a sample Tools/ directory pre-wired with [McpServerTool] attributes. Transport is set via the MCP_TRANSPORT environment variable — Stdio or Http. The Model Context Protocol is what Claude Code, VS Code Copilot, and Cursor use to discover and call external tools. Having a first-class C# template means enterprise .NET shops can now participate in the AI agent ecosystem without leaving the stack they already know. See the quickstart guide on the .NET Blog for a full walkthrough.
C# 15 Union Types: Finally Compiler-Enforced
C# developers have been asking for discriminated unions for over a decade. F# had them. Rust had them. TypeScript had something adjacent. C# had a NuGet package called OneOf and a lot of boilerplate. C# 15 fixes this with the union keyword and, critically, compiler-enforced exhaustiveness:
public record class CreditCard(string Number, string Holder, DateOnly Expiry);
public record class PayPal(string Email);
public record class BankTransfer(string Iban, string Bic);
public union PaymentMethod(CreditCard, PayPal, BankTransfer);
string Describe(PaymentMethod method) => method switch
{
CreditCard cc => $"Card ending {cc.Number[^4..]}",
PayPal pp => $"PayPal: {pp.Email}",
BankTransfer bt => $"IBAN: {bt.Iban}",
};
The switch above has no default branch and no wildcard — the compiler knows the union is exhausted. Add a fourth payment type later and the compiler forces you to handle it everywhere. Generic unions work too: public union Result<T>(T, Exception); — which replaces most custom result wrappers outright. For the full picture, Microsoft’s C# 15 feature documentation covers closed hierarchies, collection expression arguments, and the other additions in detail.
Runtime Async: Real Numbers
Runtime Async moves async state machine generation from the C# compiler into the JIT. The practical effect: async methods stop allocating objects on every invocation unless they actually suspend. Benchmarks show running 10 million awaits drops from 80 ms and 687 MB allocated on .NET 10 to 37 ms and 94 KB on .NET 11 — with zero GC gen-0 collections instead of 25. One developer independently measured a 3.2x speedup in an async microbenchmark and a real-world HTTP proxy saw 8–12% more throughput end-to-end. Runtime Async is currently opt-in; the shared framework is already built with it, and it becomes the default in .NET 12.
Everything Else Worth Knowing
- EF Core 11: Experimental vector search for SQL Server — nearest-neighbor queries without a dedicated vector DB.
- Zstandard in the BCL:
ZstandardStreamships with no external NuGet required; compresses 20–30% better than gzip at comparable speed. - Native AOT CLI host:
dotnetstarts through a Native AOT host by default, keeping MSBuild warm between invocations. - ASP.NET Core 11: Asynchronous
DataAnnotationsvalidation and OpenAPI 3.2 by default. - .NET MAUI: CoreCLR is now the default runtime across iOS, Android, and macOS.
Should You Upgrade Now?
The old “skip STS” heuristic made sense when STS meant 18 months of support. Microsoft extended STS to 24 months — .NET 11 and .NET 10 LTS now reach end-of-life on the same date. The practical calculus: if you are starting a new project or building AI agent tooling, upgrade now. If you are running a large regulated monolith where STS windows still fail procurement review, stay on .NET 10 LTS and move to .NET 12 LTS in 2027. For everyone else, the argument for waiting just got much weaker.

