.NET 11 Features: What's New in Microsoft's Latest .NET Release

Microsoft is preparing to release .NET 11, the next major version of its cross-platform development platform. The upcoming release brings improvements across the runtime, libraries, SDK, ASP.NET Core, C# 15, Entity Framework Core, .NET MAUI, and other parts of the .NET ecosystem.

As of September 2026, .NET 11 is still in preview, with the final release expected in November 2026. Microsoft has already introduced a substantial collection of features focused on performance, developer productivity, modern web development, networking, serialization, and cross-platform applications.

Let's explore the most important .NET 11 features developers should know about.

1. Runtime Async for Better Asynchronous Performance

One of the notable changes in .NET 11 is the continued development of Runtime Async.

Runtime Async moves important parts of asynchronous execution closer to the runtime itself. According to Microsoft, this can provide cleaner stack traces and reduce overhead associated with asynchronous operations.

.NET 11 also includes performance improvements such as:

• Faster async suspension
• Improved async continuations
• Better JIT compilation for async methods
• Reduced generated code size
• Reduced overhead when ExecutionContext does not need to be captured

These improvements can be particularly useful for applications that perform significant amounts of asynchronous I/O, networking, database access, or web processing.

2. C# 15 Arrives With .NET 11

.NET 11 is closely associated with C# 15, which introduces several interesting language improvements.

Microsoft's current C# 15 preview includes:

• Union types
• Closed hierarchies
• Improvements to the unsafe model
• Collection expression arguments
• Extension indexers
• Labeled break and continue
• C# 15 is scheduled to ship alongside .NET 11.

Union Types

Union types are one of the most interesting additions.

They allow developers to express that a value can be one of a specific set of types rather than simply being an arbitrary object or a type implementing a common interface.

This can make certain APIs easier to model and can make the allowed states of an application more explicit.

For developers working on large applications, stronger type modeling can reduce ambiguity and make code easier to maintain.

3. Improved .NET SDK and CLI

.NET 11 also brings several improvements to the SDK and command-line tooling.

The SDK includes support for:

• Creating and editing solution filters (.slnf) through dotnet sln
• File-based applications using #:include
• Including compiled DLL references in file-based applications
• Passing environment variables through dotnet run -e
• Improved dotnet watch
• Better crash recovery
• Aspire app-host integration
• Improved support for MAUI and mobile device selection

Microsoft has also worked on reducing the size of SDK installers on Linux and macOS through assembly deduplication.

These changes may look small individually, but they can make everyday development and command-line workflows considerably smoother.

4. Better System.Text.Json

JSON remains fundamental to modern applications, particularly REST APIs and cloud-native services.

.NET 11 expands System.Text.Json with several new capabilities, including:

• Generic type information retrieval
• Additional naming policies
• Per-member naming policy overrides
• Type-level ignore conditions
• F# discriminated union support
• Serialization of C# union types
• JSON Lines serialization
• Additional asynchronous serialization APIs

Microsoft has also added support for writing NDJSON-style output through relevant System.Text.Json APIs.

For developers building APIs and data-processing services, these improvements can reduce the amount of custom serialization code required.

5. Zstandard Compression Support

Another useful addition is Zstandard (Zstd) compression support in System.IO.Compression.

Zstandard is designed to provide a strong balance between compression ratio and speed.

.NET 11 also adds improvements around ZIP archives, including CRC32 validation and additional APIs for working with ZIP entries.

This is particularly relevant for applications that process:

• Large files
• Backups
• Data archives
• Network payloads
• Log files
• Cloud storage data

6. New Numeric APIs

.NET 11 expands the numerical capabilities of the platform.

New APIs include IEEE 754 decimal floating-point types:

• Decimal32
• Decimal64
• Decimal128

The release also introduces a generic Complex<T> type and additional numeric parsing capabilities.

These additions can be valuable for applications involving financial calculations, scientific computing, simulations, engineering, and other workloads where numerical precision and specialized numeric representations matter.

7. Networking Improvements

.NET 11 introduces several improvements to networking APIs.

The current preview includes features such as:

• HTTP request compression
• Configurable HTTP connection eviction
• DNS record resolution APIs
• Improvements to transport-related APIs

These features can help developers build more efficient network-intensive applications and services.

For cloud applications, microservices, and high-throughput APIs, improvements at the networking layer can have a meaningful impact on scalability and resource usage.

8. Expanded Process APIs

Working with operating-system processes has also received a significant update.

.NET 11 adds APIs for scenarios that previously required more manual event handling or platform-specific interop.

New functionality includes process execution helpers, fire-and-forget process launches, improved SafeProcessHandle lifecycle management, suspended process starts, and safer process lookup.

This can make applications that interact heavily with operating-system processes easier to develop and maintain.

9. ASP.NET Core and Minimal API Improvements

.NET 11 also brings important changes to ASP.NET Core.

Microsoft highlights improvements around:

• Static server-side rendering
• Form validation
• Blazor WebAssembly size
• Aspire integration
• Minimal API validation
• OpenAPI support

Minimal APIs gain asynchronous validation and support for C# union types. OpenAPI 3.2 is also set as the default in the current development of the platform.

For developers building modern web APIs, these changes can improve both API design and development productivity.

10. Blazor Improvements

Blazor continues to evolve as part of the .NET web development ecosystem.

.NET 11 includes work aimed at improving:

• Static SSR scenarios
• Form validation
• Blazor WebAssembly application size
• Development workflows
• Integration with .NET Aspire

The goal is to make Blazor more practical for modern applications while maintaining the advantages of using C# across the application stack.

Developers interested in modern Microsoft web development can also explore related ASP.NET Core development resources and technology discussions.

11. .NET MAUI and Cross-Platform Development

.NET 11 continues Microsoft's work on improving .NET MAUI.

One major area highlighted by Microsoft is the move toward CoreCLR for .NET MAUI applications on Android, iOS, and Mac Catalyst.

This work is significant because the runtime is a fundamental part of application performance and behavior.

For developers building applications across Windows, Android, iOS, and macOS, improvements to the underlying runtime can help create a more consistent development experience.

12. Cryptography Improvements

.NET 11 also expands cryptography APIs.

Among the additions is support for X25519 key agreement, providing another modern cryptographic primitive for applications that need secure key exchange.

The platform has also continued improving cryptographic APIs for verification and other security-related scenarios.

Developers should still rely on established platform cryptography APIs rather than implementing cryptographic algorithms themselves.

13. Better Compression and Archive APIs

Beyond Zstandard, .NET 11 expands support for compression and archive-related scenarios.

The current preview includes:

• Additional ZIP creation APIs
• ZIP extraction improvements
• ZIP metadata APIs
• ZIP password support
• CRC32 validation
• Improved compression APIs

These changes make the built-in .NET libraries more capable for applications that need to create, inspect, transfer, or process archives.

14. Improved Developer Tooling

Developer productivity is another major theme in .NET 11.

The SDK includes improvements to diagnostics and tooling, while dotnet watch gains capabilities such as automatic crash recovery and better integration with Aspire and mobile development.

For developers who spend a significant amount of time working from the command line, these improvements can make the development loop faster and less frustrating.

15. Updated Hardware Requirements

.NET 11 also changes minimum hardware requirements for some x86/x64 and Arm64 environments.

Microsoft says the updated requirements allow the runtime to rely on more modern instruction sets, which can improve performance and reduce maintenance complexity.

This is something organizations should consider before upgrading production environments.

Teams maintaining older hardware should verify compatibility before moving applications to .NET 11.

16. What About Entity Framework Core?

Entity Framework Core is also part of the .NET 11 development cycle.

The broader .NET 11 release includes updates across EF Core alongside the runtime, SDK, libraries, ASP.NET Core, C#, MAUI, and other technologies.

For developers building database-driven applications, it will be important to review EF Core-specific changes and migration guidance before upgrading existing applications.

Should You Upgrade to .NET 11?

If you are starting a new project, experimenting with the latest .NET ecosystem, or testing future platform capabilities, .NET 11 is worth exploring.

However, production applications should consider the release status carefully.

As of September 2026, .NET 11 remains a preview release, and Microsoft expects the final release in November 2026. Developers testing preview builds should therefore expect changes before the final version.

For existing production applications, a sensible approach is to:

• Review the .NET 11 breaking changes.
• Test dependencies and NuGet packages.
• Run automated tests against the new runtime.
• Check deployment environments and hardware compatibility.
• Review ASP.NET Core and EF Core migration requirements.
• Benchmark critical workloads.
• Upgrade to the final release after its availability.

Microsoft maintains a dedicated list of .NET 11 breaking changes, covering areas such as ASP.NET Core, runtime libraries, cryptography, networking, deployment, SDK/MSBuild, MAUI, and globalization.

.NET 11 vs Previous Versions

The biggest story behind .NET 11 isn't a single revolutionary feature. Instead, Microsoft is continuing to improve almost every layer of the platform.

Final Thoughts

.NET 11 is shaping up to be a broad platform upgrade rather than a release focused on one headline feature.

Runtime improvements target performance and asynchronous workloads, C# 15 brings new language capabilities, the SDK improves the developer experience, and libraries such as System.Text.Json, networking, compression, cryptography, and numerics continue to expand.

For web developers, improvements to ASP.NET Core, Minimal APIs, Blazor, OpenAPI, and .NET Aspire are especially interesting. Meanwhile, cross-platform developers can look forward to continued work in .NET MAUI.

Because .NET 11 is still in preview, developers should treat the current feature list as subject to change. The final release is expected in November 2026.

For developers already working with .NET, this is a good time to start testing applications against .NET 11, reviewing compatibility requirements, and exploring which new features could simplify existing code.