.NET 11

.NET 11 Arrives: C# 15 Union Types, CoreCLR in MAUI, and a Native AOT Host

.NET 11 arrives as a Standard Term Support release, and it brings meaningful change for developers who have felt the limits of older tooling. C# 15 introduces union types and closed hierarchies, while the Native AOT CLI…

4 min readInfoQ
.NET 11 Arrives: C# 15 Union Types, CoreCLR in MAUI, and a Native AOT Host

.NET 11 is the most consequential .NET release in years, and not just because it ships C# 15 with union types. Microsoft has quietly turned MAUI into a first-class CLR target and given us a native AOT host for the CLI. For teams building cross-platform desktop or mobile apps, this changes the calculus on what is practical without leaving the .NET ecosystem.

Let's start with the language. C# 15's union types and closed hierarchies are the kind of feature that looks academic on paper but solves real, daily friction. If you have ever written a method that accepts a `string | int | bool` and then manually checked each case, you know the pain. Union types let the compiler do that work, making data modeling more precise and runtime checks less necessary. Closed hierarchies, meanwhile, give you sealed type trees that pattern-match cleanly. This is not just syntactic sugar; it is the foundation for safer, more expressive domain logic. Pair this with the preview of Runtime Async, and C# begins to feel like a language designed for the concurrency patterns modern applications demand, not one retrofitting them.

The deeper story here is about where .NET runs. The native AOT CLI host means command-line tools written in .NET can now ship as single, self-contained binaries with no runtime dependency. This directly competes with Go and Rust for tooling use cases, and it is a move we have been watching take shape across the industry. Meanwhile, CoreCLR becoming the default runtime in MAUI is a signal. MAUI was always about mobile and desktop from a single codebase, but using the full CLR instead of a subset means you get the same runtime behavior, library compatibility, and debugging experience across every target. This is the kind of unification that Uno Platform 7.0 Unifies Rendering and Welcomes Apple TV to Its Ecosystem is pursuing on the rendering side, but .NET is doing it at the runtime level. For developers, this reduces the gap between "it works on my machine" and "it works on every device."

On the data side, EF Core 11 with experimental vector search is a direct response to the growing need for semantic search and AI-powered features inside relational workflows. It is not a vector database, but it does not need to be. What matters is that your existing PostgreSQL or SQL Server data can now be queried by embedding similarity without adding a second storage system. This is pragmatic: meet developers where they already store their data. It echoes the approach of DocumentDB 1.0 Brings Open Source MongoDB Compatibility to PostgreSQL, which extends an existing database with a new query model rather than asking teams to migrate. The takeaway is clear: the next generation of data tools will layer new capabilities onto proven foundations, not replace them.

The one detail to watch is how the community adopts union types in practice. They are powerful, but they also change how you design APIs. If C# teams embrace them as a first-class modeling tool, we could see a shift toward more precise, self-documenting interfaces across the ecosystem. If they are treated as an edge-case escape hatch, the impact will be muted. How frameworks like ASP.NET Core and third-party libraries handle OpenAPI 3.2 and async validation will tell us which path the ecosystem is taking.

From InfoQ

Microsoft has released .NET 11, a Standard Term Support release with two years of support. It ships C# 15 with union types and closed hierarchies, a Native AOT CLI host, a preview of Runtime Async, Zstandard compression, asynchronous validation and OpenAPI 3.2 in ASP.NET Core, CoreCLR as the default runtime in .NET MAUI, and EF Core 11 with experimental vector search.

Read the original at InfoQ