Last week, Microsoft shipped ASP.NET Core in .NET 11 as part of the wider .NET 11 release. The update spans Minimal APIs, OpenAPI, SignalR, Blazor, authentication, and the Kestrel server. As stated in the announcement, .NET 11 is a Standard Term Support release with two years of support.
On the API side, developers can now use C# 15 union types in JSON request and response bodies across Minimal APIs and MVC. The release notes limit the feature to JSON bodies, so route, query, header, and form values cannot bind to a union.
Minimal API validation also runs asynchronous validators, which keeps threads free while a rule waits on a database lookup or a remote call. The framework can now localize validation messages and display names itself, and endpoints can skip the remaining middleware pipeline through a new [ShortCircuit] attribute.
Developers who generate OpenAPI documents now get version 3.2 unless they select an earlier one for tooling that has not caught up. As described in the release notes, the framework depends on Microsoft.OpenApi 3.3.1 for this, and the notes label that update a breaking change.
With 3.2, endpoints that stream server-sent events are documented with a schema for each event's payload, and the generator emits an anyOf schema for unions. Generated documents can also describe endpoints that use the HTTP QUERY method, and APIs that carry the [Obsolete] attribute show up as deprecated.
SignalR adds authentication refresh, so a long-lived connection no longer has to close when its access token expires. As reported, server developers enable it per hub, while the .NET client refreshes automatically by default and the TypeScript client can do the same. Blazor passes the refreshed identity on to Interactive Server components while the circuit stays connected.
Blazor receives the longest list of changes, and many of them target static server-side rendering. With the new CacheView component, developers can cache the rendered markup of a component subtree, and the child components do not run when a cached copy is served. Blazor now ships client-side validation for static SSR forms, enabled by default.
Developers can also carry data between requests with TempData or session values. According to the release notes, the Blazor Web App template drops its app.UseAntiforgery() call, because a middleware for CSRF protection is now added by default.
For Interactive Server apps, an opt-in package pauses the circuit of a hidden browser tab after a delay, two minutes by default, to free server memory. Lists built with Virtualize may now mix items of different heights, and Microsoft raised the default OverscanCount from 3 to 15. Page and sort state in QuickGrid now lives in the URL query string, with sortable headers and pager controls rendered as links instead of buttons.
The release notes flag this as a CSS breaking change, because custom styles written for the buttons also have to target the links. The release also includes Microsoft.AspNetCore.Components.AI, a set of components for chat and agent interfaces. According to the announcement, Microsoft treats that package as experimental and will keep it in prerelease throughout .NET 11.
On the security and server side, an experimental package adds Device Bound Session Credentials, a protocol that ties session refresh to a private key held by the browser. Response compression and request decompression gain Zstandard support, which is on by default.
Kestrel's HTTP/1.1 parser no longer throws exceptions on malformed requests, a change that is reported to raise throughput by up to 20 to 40 percent under heavy invalid traffic. The shared framework libraries of ASP.NET Core are now compiled with runtime-async, described in the release notes as an internal change with no public API impact.
Two older APIs are on the way out. The Microsoft.AspNetCore.Grpc.Swagger package is now deprecated, and Kestrel's TlsClientHelloBytesCallback option is obsolete in favor of the new UseTlsClientHelloListener extension.
Other changes in this release are native OpenTelemetry tracing attributes, client-side cancellation of SignalR hub invocations, scrolling to a specific item in Virtualize and QuickGrid, passkey display names inferred from the authenticator, and TimeProvider support in ASP.NET Core Identity.
For interested readers and developers, the full release notes are available in the What's new in ASP.NET Core in .NET 11 article on Microsoft Learn.