.NET 11 RC2: What's New and What Developers Should Test Before Release

Released on October 13, 2026, .NET 11 RC2 focuses on refining capabilities introduced throughout the preview cycle, improving developer tooling, and addressing issues before the final release.

In our .NET 11 Preview 4 engineering review, we examined improvements to process management, runtime behavior, and performance from the perspective of developers building and maintaining .NET libraries.

RC2 builds on that progress with updates across ASP.NET Core, libraries, NuGet, MSBuild, Windows Forms, and other areas.

Like RC1, RC2 comes with Microsoft's go-live support license, allowing production use with Microsoft support during its limited support window.

So what has changed, and what should developers test before upgrading?

What's New in .NET 11 RC2?

The RC2 release covers several areas of the .NET ecosystem, including ASP.NET Core, runtime behavior, libraries, NuGet, MSBuild, Windows Forms, F#, and .NET MAUI.

Not every improvement will affect every application. The most useful approach is to identify changes that intersect with your existing code and test those areas first.

1. ASP.NET Core: QuickGrid Virtualization APIs Are No Longer Experimental

Developers building Blazor applications with large data sets will appreciate this update.

In .NET 11 RC2, the QuickGrid virtualization APIs are no longer experimental.

Virtualization allows applications to render only the items needed for the visible portion of a grid instead of rendering the entire data set at once.

What developers should test:

• Grid rendering with large data sets.
• Scrolling responsiveness and row loading.
• Data fetching and pagination behavior.
• Compatibility with existing Blazor components.

The change doesn't automatically make every grid faster. Actual performance still depends on data retrieval, rendering complexity, and how virtualization is configured.

2. .NET Libraries: Streaming, Validation, and HTTP/2 Improvements

Several library updates in RC2 are worth examining, particularly for applications processing structured data or handling high-throughput requests.

Incremental CBOR Reading

.NET 11 RC2 introduces support for reading Concise Binary Object Representation (CBOR) incrementally.

CBOR is a compact binary data format commonly used in environments where message size and processing efficiency matter.

What to test: Compare your existing CBOR parsing workflow with incremental reading, particularly around buffering, incomplete messages, and memory usage.

Configurable Initial HTTP/2 Concurrency

Developers can now configure initial HTTP/2 concurrency behavior.

This provides another tuning option for applications that rely heavily on HTTP/2 communication.

However, increasing concurrency settings doesn't guarantee better throughput. Performance depends on workload characteristics, server limits, and resource availability.

What to test: Run representative HTTP/2 workloads and compare throughput, latency, and resource consumption before changing production settings.

Experimental Cryptography APIs

RC2 also introduces experimental composite ML-KEM and Hybrid Public Key Encryption (HPKE) APIs.

These additions are relevant to developers exploring modern encryption techniques and post-quantum cryptography.

Because the APIs are experimental, teams should evaluate their suitability and stability before relying on them in long-lived production systems.

3. SDK and MSBuild: Improvements to Developer Tooling

.NET 11 RC2 introduces several improvements to the SDK and MSBuild, including support for quoted file-level directive values, MSBuild properties in launch-profile arguments, and faster wildcard matching during project evaluation.

These changes can simplify build configuration and improve development workflows, particularly for projects with complex build requirements.

Developers working with Iron Software libraries can also explore our Visual Studio 2026 and Iron Software integration guide for examples of setting up .NET development projects, installing packages, and working with document-processing libraries.

The guide covers existing supported frameworks; it should not be interpreted as confirmation of .NET 11 compatibility.

4. F# and .NET MAUI Updates

RC2 also introduces improvements for developers working with F# and cross-platform applications.

F# Improvements

The release includes:

• Runtime async support.
• Reduced allocations in FSharp.Core collections.
• Compiler memory usage improvements.
• Support for reraise in computation expressions.
• Improvements involving concurrent asynchronous work.
• Trimming and Native AOT improvements.

These updates are particularly relevant to applications using asynchronous processing, large collections, or ahead-of-time compilation.

.NET MAUI Improvements

.NET MAUI receives updates involving:

• Creating applications with C# UI.
• Apple Icon Composer assets.
• An Apple Shell handler available for evaluation.
• XAML authoring and Hot Reload improvements.

Developers maintaining MAUI applications should test the relevant tooling and platform behavior before adopting these changes.

How to Test .NET 11 RC2 Before Upgrading

Reading release notes is useful, but the most important question is whether your application behaves correctly on the new runtime.

Start by installing the .NET 11 RC2 SDK, creating a separate test branch, and updating your target framework.

Then restore dependencies, build the application, and run automated tests.

Passing these checks doesn't guarantee runtime compatibility.

Applications using platform-specific dependencies, native components, or document-processing libraries should also undergo integration and deployment testing.

For example, teams running document-processing workloads in containers can refer to our IronBarcode Docker and Linux setup guide for an example of the operating-system and container dependencies that may need attention.

Use a staging environment that closely resembles production, and validate application behavior before deploying.

.NET 11 vs. .NET 10: Should You Upgrade?

.NET 11 is approaching general availability, but upgrading immediately isn't necessary for every application.

.NET 10 is a Long Term Support (LTS) release, with support scheduled through November 2028. .NET 11 is a Standard Term Support (STS) release, offering newer platform capabilities with a shorter support lifecycle.

For teams prioritizing long-term stability, .NET 10 remains a strong option.

For developers interested in newer runtime and framework improvements, .NET 11 may be worth evaluating after compatibility testing.

If you're maintaining applications with third-party libraries, our .NET 10 readiness article provides additional context on how Iron Software approached compatibility testing during the previous .NET release cycle.

The important consideration is not simply which version is newer, but which version best fits your application's requirements, dependencies, and maintenance schedule.

.NET 8 and .NET 9 End of Support: What Developers Should Know

Microsoft will end support for both .NET 8 and .NET 9 on November 10, 2026.

After that date, these versions will no longer receive regular security updates and technical support under Microsoft's lifecycle policy.

For teams still running applications on these frameworks, migration planning should already be underway.

However, .NET 11 isn't the only upgrade option. .NET 10 LTS provides a longer support lifecycle and may be better suited to applications requiring extended stability.

We've covered these considerations in more detail in Why Staying Current Matters: Planning Your .NET 10 Migration, including the distinction between framework compatibility and ongoing optimization.

Whichever version you choose, make sure your migration plan includes third-party dependencies, deployment environments, and regression testing.

Final Thoughts: Is .NET 11 RC2 Ready for Your Application?

.NET 11 RC2 may not introduce the same volume of headline features as earlier previews, but it represents an important milestone before general availability.

For developers, the most valuable next step is to test the changes that actually affect their applications.

Microsoft's go-live support makes RC2 an option for production use, but teams should account for its limited support window and plan to move to the final release when available.

And if your applications are still running on .NET 8 or .NET 9, now is also the time to finalize a migration plan to a supported version.

The real question isn't simply what's new in .NET 11. It's whether your application, its dependencies, and its deployment environment are ready for it.

Take Your Next .NET Project Further

Exploring .NET 11 is just one part of building modern .NET applications. If your next project involves generating PDFs, reading Excel files, or extracting text from documents, Iron Software offers developer libraries designed for these workflows.

Start with Iron Software to explore PDF generation and document processing in C#.

Start Your Free Trial