.NET 11 Lands: C# Unions, Async Validation, and Built-In AI Agents for ASP.NET Core

Microsoft shipped .NET 11 on November 10, 2026, and the headline features span the whole stack — from a language change in C# 15 that developers have been waiting years for, to a reworked approach to building web apps that natively understand AI agents. It's a Standard-Term Support release, meaning it gets updates through November 2028. If you're still on .NET 8 or 9, those end-of-life at the same time .NET 11 ships, so this release also carries a nudge: migrate now.

Discriminated unions finally land in C#

The biggest language addition in C# 15 is union types — the ability to declare a type that can hold exactly one of several named variants. InfoQ's breakdown of ASP.NET Core in .NET 11 explains how this flows through to web apps: ASP.NET Core now supports C# unions anywhere it uses System.Text.Json, which means union-typed request and response bodies work out of the box in Minimal APIs and MVC controllers. Route, query, and form values can't bind to unions yet, but the foundation is there.

Union types solve a problem that C# developers have been working around with sealed class hierarchies, enums with associated data, or one-of-N pattern matching workarounds for a long time. The addition lands C# closer to the expressiveness of F# and Rust's enum variants, without abandoning the class-based OOP model the ecosystem is built on.

Async validation in ASP.NET Core

ASP.NET Core gains asynchronous validation in .NET 11. The obvious use case is a form field that needs a database lookup before it can confirm validity — checking whether a username is taken, for example — without blocking the thread. Previously this required either custom validation attributes that bent the synchronous validation model, or moving the check out of validation entirely. The new async path integrates cleanly with the existing IValidatableObject and data annotation model.

Built-in AI agent hosting

The most forward-looking addition is integration with the Microsoft Agent Framework for ASP.NET Core. You can now host AI agents directly inside an ASP.NET Core app, with built-in support for the OpenAI responses protocol, agent-to-agent orchestration, and AG-UI for streaming real-time updates from agents back to the browser. The Blazor AI Components package — which provides prebuilt UI for interacting with agents in Blazor apps — ships as experimental in .NET 11, meaning the API may still change.

This positioning is deliberate. Microsoft is betting that the next generation of web apps won't be purely data CRUD with a React frontend — they'll involve agents in the backend, and ASP.NET Core wants to be a natural home for those workloads.

Blazor and runtime changes

Visual Studio Magazine notes that .NET MAUI gets CoreCLR in .NET 11, replacing the Mono runtime for desktop targets — a performance improvement for cross-platform desktop apps. Blazor gains session and culture persistence, the EnvironmentView component, circuit auto-pause, and static SSR subtree caching. SignalR adds client-side cancellation of hub method invocations, which closes a long-standing gap in bidirectional communication patterns.

Runtime Async, the low-level coroutine model Microsoft has been developing, stays in preview for .NET 11. It's the kind of change that needs careful baking before shipping, so the preview status isn't surprising.

Upgrading

.NET 11 is available now for Windows, Linux, and macOS. The official announcement post includes migration notes. For teams on .NET 8 or 9, the end-of-support deadline arriving alongside this release makes the upgrade timeline less optional than usual — start the migration checklist now rather than in spring 2027.