NET 11 : ASP.NET Core: Union Type Support
Microsoft shipped ASP.NET Core in .NET 11 with C# 15 union types, default OpenAPI 3.2 schemas, Blazor CacheView, and 40 percent faster malformed HTTP parsing.
By Dillip Chowdary • Nov 19, 2026 • Source: InfoQ

At a glance
- Product
- ASP.NET Core in .NET 11
- Support Model
- Standard Term Support with two years of support
- Release Date
- November 2026
- Availability
- Generally available across Minimal APIs, MVC, and Blazor
- Core Limit
- C# 15 union types limited strictly to JSON bodies
- Experimental AI
- Microsoft.AspNetCore.Components.AI in prerelease
In this post
Microsoft shipped ASP.NET Core in .NET 11 as part of the wider .NET 11 release, establishing a Standard Term Support baseline with two years of official support. According to InfoQ's report, the release delivers targeted updates across Minimal APIs, OpenAPI, SignalR, Blazor, authentication protocols, and the Kestrel server. The engineering updates focus on request throughput, automated contract documentation, client-side rendering performance, and connection durability.
This architectural breakdown covers the runtime revisions, serialization boundaries, and component changes across the web framework. Backend engineers, API architects, and frontend developers building with Blazor gain direct visibility into breaking changes, deprecated libraries, and performance benchmarks. Teams evaluating the standard support cycle can assess operational throughput gains alongside component lifecycles before planning upgrades.
01Union types and asynchronous validation
Minimal APIs and MVC endpoints now support C# 15 union types within JSON request and response bodies. This allows endpoint handlers to serialize and deserialize polymorphic data models without custom converters. Validation pipelines in Minimal APIs now run asynchronous validators, keeping threads free while rules execute database lookups or remote service calls.
The framework localizes validation messages and display names internally, removing the requirement for custom localization boilerplate. Developers can also decorate route endpoints with the new [ShortCircuit] attribute to bypass remaining middleware stages once request execution finishes, reducing overhead across lightweight health checks and high-volume utility routes.
Note: The framework limits C# 15 union type binding strictly to JSON request and response bodies across Minimal APIs and MVC controllers. Route parameters, query strings, request headers, and standard form submissions cannot bind to a union. Handlers processing non-JSON payload segments must continue using concrete scalar types or explicit model binders.
02Default OpenAPI specifications and credential refresh
ASP.NET Core now targets OpenAPI 3.2 by default during document generation unless developers explicitly pin an older schema version. The implementation depends on Microsoft.OpenApi 3.3.1, an update labeled as a breaking change in the official release notes. Endpoints streaming server-sent events emit dedicated schemas for event payloads, while endpoints using union types generate matching anyOf schemas.
The OpenAPI document generator also maps endpoints using the HTTP QUERY method and automatically marks routes carrying the [Obsolete] attribute as deprecated. Meanwhile, SignalR introduces authentication refresh capabilities to maintain persistent connections across access token rotations. Long-lived duplex connections no longer terminate when security tokens expire, as servers configure refresh policies per hub while .NET and TypeScript clients handle refreshes automatically.
03Subtree caching and interactive server circuits
Blazor gains rendering improvements aimed at static server-side rendering, highlighted by the new CacheView component. Developers use CacheView to cache the rendered markup of component subtrees, skipping child component execution entirely whenever serving cached markup. In addition, static server-rendered forms include client-side validation enabled by default, and developers can pass state between requests using TempData or session values.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
The Blazor Web App template drops its app.UseAntiforgery() call because cross-site request forgery protection middleware is added by default. For Interactive Server applications, an opt-in package pauses the active circuit of hidden browser tabs after a delay of two minutes by default to free server memory. Lists built with Virtualize accept items of varying heights with default OverscanCount raised from 3 to 15, and QuickGrid renders sort headers and pagers as links with state stored in URL query strings.
04Parser throughput gains and compression benchmarks
Kestrel's HTTP/1.1 parser removes exception-throwing logic when processing malformed HTTP requests, handling invalid traffic with dedicated parser states instead. Benchmark measurements report that eliminating parsing exceptions increases server throughput by 20 to 40 percent under heavy volumes of invalid traffic. Furthermore, ASP.NET Core enables Zstandard response compression and request decompression by default across the network stack.
Underneath the public surface, shared framework libraries are now compiled with runtime-async, delivering internal threading optimizations without altering public application programming interfaces. Security layers introduce an experimental Device Bound Session Credentials package that locks session refresh operations to a hardware-backed private key on the browser. The release also adds native OpenTelemetry tracing attributes, passkey display names inferred from authenticators, and TimeProvider support in ASP.NET Core Identity.
| Feature Area | Prior Configuration | .NET 11 Specification |
|---|---|---|
| Virtualize Component Overscan | 3 items | 15 items |
| Malformed HTTP/1.1 Parser Throughput | Baseline with exceptions | 20 to 40 percent throughput gain |
| Inactive Tab Circuit Pause Delay | Continuous connection | 2 minutes by default |
| Default OpenAPI Specification Version | Prior schema versions | OpenAPI 3.2 via Microsoft.OpenApi 3.3.1 |
| Zstandard Payload Compression | Disabled by default | Enabled by default |
05Package installations and migration paths
Microsoft introduces Microsoft.AspNetCore.Components.AI to deliver prebuilt interface controls for chat applications and autonomous agent systems. The framework engineering team designated this package as experimental, keeping it in prerelease status throughout the .NET 11 support lifecycle. Development teams can install the experimental component library directly from package feeds into existing web projects using standard package management tooling.
dotnet workload updatedotnet add package Microsoft.AspNetCore.Components.AI --prereleaseUpgrades require attention to breaking changes and library deprecations across the server stack. The Microsoft.AspNetCore.Grpc.Swagger library is deprecated, and Kestrel obsoletes the TlsClientHelloBytesCallback delegate in favor of the UseTlsClientHelloListener extension method. Teams styling QuickGrid tables must update custom CSS selectors, as pager and sort headers now render as anchor tags rather than button elements.
Applications utilizing SignalR also gain client-side invocation cancellation, enabling browser clients to cancel in-flight hub requests immediately. Developers can update SDK workloads through the command line interface to align development environments with the latest standard term release. Comprehensive technical details and migration guidance remain documented in the What's new in ASP.NET Core in .NET 11 guide on Microsoft Learn.
Frequently asked questions
What support lifecycle applies to ASP.NET Core in .NET 11?
Microsoft designated .NET 11 as a Standard Term Support release. It receives active support and maintenance for two years following its launch.
Can C# 15 union types be used in route parameters or query strings?
No, union type binding is limited to JSON request and response bodies. Route parameters, query parameters, request headers, and form inputs cannot bind to union types.
How does Kestrel improve HTTP/1.1 request handling throughput?
Kestrel's HTTP/1.1 parser no longer throws exceptions when encountering malformed requests. This optimization raises request throughput by 20 to 40 percent under heavy invalid traffic.
What breaking changes are introduced in OpenAPI and QuickGrid?
The framework upgrades default schema generation to OpenAPI 3.2 via Microsoft.OpenApi 3.3.1, which breaks tooling lacking 3.2 support. In QuickGrid, sortable headers and pagination controls render as HTML links rather than buttons, requiring CSS style updates.
Sources
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement