Ready for .NET 11: Day-Zero Support Across the Telerik Portfolio

The Progress Telerik portfolio of products is ready for .NET 11 support so you won’t miss a step.

With Microsoft’s .NET 11 release, Progress is shipping Telerik products with day-zero support for .NET 11. Development teams can start exploring the latest platform improvements immediately and move to production on their own schedule.

Each new .NET release brings improvements across the runtime, developer tooling and application frameworks. .NET 11 continues that work with updates for web and cross-platform development. Telerik customers can adopt the new platform and continue using the Telerik tools they rely on across their application stack.

.NET 11 Support Across Telerik Products

Every major Telerik UI library, reporting, document processing and mocking solution is ready from day one. Whether you’re building web, desktop, mobile or document-processing workflows, you can upgrade with confidence and continue using the Telerik solutions you rely on today.

• Telerik UI for Blazor is compatible with .NET 11.
• Telerik UI for ASP.NET Core is compatible with .NET 11 and can be used alongside the platform improvements without requiring corresponding changes to Telerik components.
• Telerik UI for .NET MAUI supports .NET 11 from day one.
• Telerik UI for WinForms and Telerik UI for WPF are compatible with .NET 11.
• Telerik Reporting is compatible with .NET 11. While the release includes runtime-level async improvements, the Reporting engine is not heavily async-based, so we do not expect those changes to have a significant performance impact on the engine.
• Telerik Document Processing Libraries are compatible with .NET 11.
• Telerik Visual Studio and Visual Studio Code extensions support .NET 11 development workflows.
• Telerik JustMock supports .NET 11 Runtime Async scenarios.

What .NET 11 Brings to Blazor

.NET 11 brings a wide range of Blazor improvements. Here are a few highlights we picked because they are especially relevant to apps built with Telerik UI for Blazor components:

• The new DisplayName component and support for Display and DisplayName attributes make it easier to show a field’s display name, for example, in a <label> within a Telerik Form item template.
• Asynchronous form validation supports validation workflows that depend on asynchronous value checks.
• Client-side prerendering preserves the server’s culture, helping maintain consistent localized output.
• A new development server for Blazor WebAssembly apps brings an updated development experience.
• Server-triggered circuit pause and automatic circuit pause on tab inactivity give apps more ways to manage resources for inactive Blazor Server sessions.

These are framework-level capabilities you can use in any Blazor app, and they work hand in hand with Telerik UI for Blazor. Because the library supports a broad range of .NET versions, the same Telerik package works across your .NET 10 and .NET 11 projects, so you can adopt the latest framework features at your own pace.

For more details, see Microsoft’s ASP.NET Core 11 release notes.

.NET MAUI 11: Unified Runtime, Faster Builds, Higher Quality

With .NET 11, Microsoft is putting the emphasis on .NET MAUI quality while continuing to modernize the framework underneath. The move to CoreCLR, improvements to XAML compilation and Native AOT support bring .NET MAUI closer to the rest of the .NET platform, giving developers a more consistent runtime and development experience.

Runtime and Performance

• CoreCLR becomes the default runtime for Android, iOS, Mac Catalyst and tvOS, replacing Mono and bringing .NET MAUI onto the same runtime foundation as the rest of .NET. The change opens the door to improvements in debugging, profiling, Hot Reload and runtime performance. Learn more in .NET MAUI Moves to CoreCLR in .NET 11.
• Native AOT publishing is available as an opt-in option for scenarios where startup performance and application size are important.

Developer Experience

• XAML source generation is now the default, moving XAML compilation to source generation and helping improve build performance while bringing Debug and Release builds closer together.
• HybridWebView gets better Native AOT and trimming support through source-generated JSON serialization for JavaScript-to-.NET calls, making hybrid applications better suited for fully trimmed and AOT-compiled deployments.

Platform Alignment

• Material 3 support on Android brings .NET MAUI applications in line with Google’s latest Material design system and modern Android experiences.
• Xcode 27 readiness helps developers prepare existing Apple applications for platform changes, including the updated scene lifecycle.

The result? A more unified .NET foundation, quicker development cycles and better alignment with the platforms your apps run on.

With Telerik UI for .NET MAUI supporting .NET 11 from day one, developers can take advantage of the new runtime and tooling improvements while continuing to build polished, production-ready cross-platform experiences.

For the full list of changes, see What’s new in .NET MAUI for .NET 11.

JustMock and Runtime Async

.NET 11 advances Runtime Async, a runtime-managed approach to asynchronous execution that changes how some async methods are represented and executed. Instead of relying on the traditional compiler-generated state machine, these methods use a runtime-managed model.

The JustMock CodeWeaver profiler detects Runtime Async methods during JIT compilation and uses a dedicated interception path at async suspension and resumption points. Methods that continue to use the traditional compiler-generated state machine remain supported through the existing JustMock interception path. The profiler also excludes runtime async helper intrinsics from instrumentation to prevent recursive profiling.

This means teams can continue using Telerik JustMock for asynchronous scenarios on .NET 11, including Task<T>, ValueTask<T> and static async methods, as well as exception propagation across async suspension boundaries.

Plan Your Next Upgrade

Microsoft has scheduled the end of support for .NET 8 and .NET 9 for November 10, 2026, and support for .NET Framework 4.6.2 is scheduled to end on January 12, 2027. While these dates are set by Microsoft, Progress will continue to support these versions in Telerik products until February 2027. This additional window is designed to allow a smooth transition for teams still running on .NET 8 or .NET 9, giving them enough time to plan and complete their migration without disruption.

If your applications still target these frameworks, now is a good time to review your upgrade plans. Refer to Microsoft’s .NET and .NET Core support policy, .NET Framework support policy, .NET Framework lifecycle page and the announcement that .NET 8 and .NET 9 will reach end of support on November 10, 2026.

Whether you’re modernizing existing applications or starting new projects, .NET 11 provides the latest platform capabilities while Telerik delivers the UI, reporting, mocking and document-processing tools you need to build production-ready applications from day one.