Starting in .NET 11 Preview 4, .NET MAUI apps on Android, iOS, and Mac Catalyst now run on CoreCLR by default—the same runtime that powers ASP.NET Core, Azure, and millions of production workloads. This shift ends a 15-year era of Mono being the default for mobile .NET development. Here are seven key things you need to know about this transition.
1. CoreCLR Takes Over as Default Runtime for Mobile
In .NET 11 Preview 4, CoreCLR becomes the default runtime for .NET MAUI applications targeting Android, iOS, Mac Catalyst, and tvOS. This means your mobile and embedded apps now run on the same high-performance runtime used by ASP.NET Core, Azure services, desktop applications, and countless production systems worldwide. The change applies to both Release and Debug builds, offering a unified runtime environment across all major .NET platforms. For the first time, mobile developers benefit from the same JIT compiler, garbage collector, and diagnostics tooling available to server and desktop developers.
2. Mono’s Legacy: The Foundation That Made This Possible
For over 15 years, Mono enabled .NET on platforms it was never designed for. Started by Miguel de Icaza in 2001 to bring .NET to Linux, Mono grew far beyond that. It powered MonoTouch (C# on iPhone in 2009) and MonoDroid (Android), which became Xamarin—a platform used by millions of developers. Unity built its entire scripting runtime on Mono, and it also underpins Avalonia, Uno Platform, MonoGame, and Godot’s C# backend. Mono proved .NET could run anywhere, and CoreCLR’s takeover is the next chapter, not an ending.
3. What Actually Changed in .NET 11
When you build a .NET MAUI app targeting .NET 11, the default runtime for Android, iOS, Mac Catalyst, and tvOS is now CoreCLR. This is an extension of the CoreCLR platform support that already existed for Windows, Linux, macOS (AppKit), and Android. The key change is that the last remaining .NET MAUI platforms—those that still relied on Mono—have now migrated. For detailed technical differences, refer to the Runtimes and compilation documentation.
4. Platforms Affected—and One That Isn’t
- Affected: Android, iOS, Mac Catalyst, and tvOS—all move to CoreCLR.
- Not affected: Blazor WebAssembly continues to use Mono, and this does not change in .NET 11.
- Opt-out available: If you encounter issues during the transition, you can opt back to Mono via a project setting.
This clarification prevents confusion—mobile and desktop targets run CoreCLR, while WebAssembly scenarios remain on Mono for now.
5. Why CoreCLR? Three Driving Reasons
Runtime unification: Before, mobile apps ran on Mono while servers, desktops, and cloud ran on CoreCLR—creating splits in JIT behavior, garbage collection, diagnostics, and bug surfaces. Now, one runtime spans all platforms.
Performance: CoreCLR brings years of optimizations from ASP.NET Core and Azure to mobile, including better startup, lower memory, and faster execution.
Tooling: Developers access a single set of diagnostic tools (dotnet-counters, dotnet-dump, etc.) across all environments, simplifying debugging and profiling.
6. Impact on the Broader .NET Ecosystem
Mono’s reach extends well beyond Microsoft. Unity uses Mono for its scripting runtime and has begun its own transition to CoreCLR. Avalonia and Uno Platform leverage Mono on WebAssembly for cross-platform browser apps. MonoGame carries XNA game development to every platform, and Godot’s C# backend relies on Mono. This migration signals that CoreCLR is now the standard for .NET, and the entire ecosystem will likely follow. The change reduces fragmentation and accelerates improvements for all .NET developers.
7. How to Opt Back to Mono If Needed
Microsoft acknowledges that the transition may cause temporary issues. To revert to Mono for your .NET MAUI project in .NET 11, set the MonoRuntimeEnabled property to true in your project file:
<PropertyGroup>
<MonoRuntimeEnabled>true</MonoRuntimeEnabled>
</PropertyGroup>This opt-out is intended for compatibility during the transition. Long-term, CoreCLR is the path forward, and Microsoft encourages developers to report issues and help shape the final runtime integration.
Conclusion
The move to CoreCLR in .NET 11 is a landmark unification for .NET MAUI. It brings mobile development into the same high-performance environment as server and desktop, while honoring Mono’s legacy. Developers should test their apps, take advantage of the opt-out if needed, and prepare for a future where one runtime powers all .NET workloads.