🧩Microsoft Ships .NET 11 With C# 15 Union Types and OpenAPI 3.2 by Default
Your JSON APIs just got typed unions, and your docs got an upgrade
TL;DR
Microsoft shipped .NET 11 alongside ASP.NET Core with C# 15 union types for JSON bodies, OpenAPI 3.2 by default, and a long Blazor changelog. It's a Standard Term Support release, so you get two years of patches. If you run ASP.NET Core APIs, the OpenAPI default alone can break your tooling.
Microsoft released .NET 11 with ASP.NET Core, and the headline feature is C# 15 union types, which now work in JSON request and response bodies across Minimal APIs and MVC. The catch: unions only bind to JSON bodies. Route, query, header, and form values can't use them, so don't plan a full migration yet. If you maintain APIs, the bigger surprise is the OpenAPI default. Documents now generate as version 3.2 unless you pin an earlier version, and that depends on Microsoft.OpenApi 3.3.1, which is a breaking change. Check your document generation and any downstream codegen before you upgrade. Server-sent event endpoints now get per-event payload schemas, and the HTTP QUERY method is documented too. Blazor got the most changes, many aimed at static server-side rendering. The new CacheView component caches rendered markup for a component subtree, client-side validation is on by default for static SSR forms, and the Blazor Web App template no longer needs app.UseAntiforgery() because CSRF middleware is added automatically. Watch the Virtualize default OverscanCount jump from 3 to 15, which changes render behavior for existing lists.

Key Points
Minimal API validation now runs asynchronous validators, so a rule waiting on a database lookup or remote call no longer blocks a thread while it waits.
Keep reading — it's free
Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.
Already a member? Sign in
Comments
Be the first to comment