Microsoft shipped .NET 11, which includes ASP.NET Core as part of the broader release. This update covers various components such as Minimal APIs, OpenAPI, SignalR, Blazor, authentication, and the Kestrel server. .NET 11 is designated as a Standard Term Support release, providing two years of support.
Developers can now use C# 15 union types within JSON request and response bodies across Minimal APIs and MVC. This feature is limited to JSON bodies and does not apply to route, query, header, or form values. Minimal API validation now supports asynchronous validators, which helps keep threads free during database lookups or remote calls. The framework can also localize validation messages and display names, and a new [ShortCircuit] attribute allows endpoints to bypass the remaining middleware pipeline.
OpenAPI document generation now defaults to version 3.2, unless an earlier version is explicitly selected. This update relies on Microsoft.OpenApi 3.3.1 and is labeled as a breaking change. OpenAPI 3.2 documents endpoints that stream server-sent events with a schema for each event's payload, and generates an anyOf schema for unions. It also describes endpoints using the HTTP QUERY method and marks APIs with the [Obsolete] attribute as deprecated.
SignalR now includes authentication refresh, preventing long-lived connections from closing when their access tokens expire. Server developers enable this feature per hub, while the .NET client refreshes automatically by default, and the TypeScript client can be configured to do the same. Blazor passes the refreshed identity to Interactive Server components while the circuit remains connected.
Blazor received the most extensive list of changes, many of which target static server-side rendering. A new CacheView component allows developers to cache the rendered markup of a component subtree, preventing child components from running when a cached copy is served. Blazor now ships with client-side validation for static SSR forms, enabled by default. Developers can also carry data between requests using TempData or session values. The Blazor Web App template no longer includes app.UseAntiforgery() because CSRF protection middleware is now added by default. For Interactive Server apps, an opt-in package pauses the circuit of a hidden browser tab after a delay.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
Microsoft released .NET 11, which includes updates to ASP.NET Core, Minimal APIs, OpenAPI, SignalR, and Blazor. This release introduces C# 15 union type support in JSON bodies, defaults to OpenAPI 3.2, and adds authentication refresh for SignalR connections. Blazor also received significant changes, including a CacheView component and client-side validation for static SSR forms.