Unified Runtime: .NET MAUI Embraces CoreCLR in .NET 11

Introduction

With the arrival of .NET 11 Preview 4, .NET MAUI applications on Android, iOS, and Mac Catalyst now run on CoreCLR by default. This marks a significant milestone: mobile apps share the same runtime that powers ASP.NET Core, Azure services, desktop apps, and countless production environments worldwide. It’s a move toward unification that promises smoother development, better performance, and fewer surprises across platforms.

The Legacy of Mono

For over fifteen years, the Mono project served as the backbone for .NET on platforms where the original runtime couldn’t go. Miguel de Icaza launched Mono in 2001 with a vision to bring .NET to Linux. That initial spark grew into something far-reaching.

From Linux to Mobile

Mono’s reach expanded quickly: MonoTouch brought C# to the iPhone in 2009, and MonoDroid followed for Android. These experiments evolved into Xamarin, a platform that enabled millions of developers to ship production mobile apps. When Microsoft acquired Xamarin in 2016 and began building .NET MAUI, Mono remained the runtime beneath the surface.

The Mono Ecosystem

Mono’s influence goes well beyond Microsoft. Unity built its entire scripting engine on Mono, powering one of the world’s most popular game engines. Unity itself is now transitioning to CoreCLR. Avalonia UI relies on Mono to bring .NET desktop applications to Linux. Uno Platform uses Mono on WebAssembly for cross‑platform browser apps. MonoGame carries forward the XNA legacy for .NET game development on every platform. Godot offers a C# scripting backend powered by Mono.

This vast ecosystem all shares the same foundation. Mono didn’t just enable .NET on mobile; it proved .NET could thrive anywhere. CoreCLR becoming the default for .NET MAUI is the next chapter in that story, not its conclusion.

What Changes in .NET 11

When you build a .NET MAUI app targeting .NET 11, CoreCLR is now the default runtime for both Release and Debug builds on Android, iOS, and Mac Catalyst. This is not entirely new territory—CoreCLR has been extended to Windows, Linux, macOS (AppKit), and Android in earlier releases. What’s new in .NET 11 is that the same runtime now covers all .NET MAUI platforms, including iOS and Mac Catalyst, which were previously still on Mono.

A few important clarifications:

• This change applies to Android, iOS, Mac Catalyst, and tvOS — all move to CoreCLR.
• Blazor WebAssembly continues to use Mono; that is not changing in .NET 11.
• If you encounter issues during the transition, you can opt back to Mono by adjusting your project settings.

For deeper insight into runtime and compilation across platforms, check the Runtimes and compilation documentation.

Why CoreCLR Makes Sense

Three main drivers motivated this change.

Runtime Unification

Until now, mobile apps ran on Mono while server, desktop, and cloud workloads used CoreCLR. That split meant different JIT behavior, garbage collection characteristics, diagnostics tooling, and even different bug surfaces. With CoreCLR across all platforms, your mobile app runs on the exact same runtime as your backend. This reduces the cognitive load for developers and eliminates platform‑specific surprises.

Performance and Tooling

CoreCLR brings continuous improvements in just‑in‑time compilation, garbage collection, and debugging. Unified diagnostics mean tools like dotnet counters, dotnet trace, and performance profilers work identically on mobile devices. Memory management, thread pool behavior, and exception handling become consistent, making it easier to optimize and troubleshoot your apps.

Transition and Compatibility

For most existing .NET MAUI projects, the switch to CoreCLR should be transparent. However, if your code relies on Mono‑specific behaviors or third‑party libraries that have not yet been updated, you can temporarily opt back to Mono. Microsoft provides project settings to control the runtime choice during this transition period. It is recommended to test your app thoroughly on all target platforms after upgrading to .NET 11.

Looking Ahead

This move completes a long‑standing goal: a single, high‑performance runtime that runs everywhere .NET runs. It also acknowledges the immense contributions of the Mono project and the ecosystem built around it. As Unity, Avalonia, and others adopt CoreCLR, the entire .NET landscape becomes more unified. For mobile developers, the promise is simpler development, fewer edge cases, and the full power of modern .NET tooling in your pocket.