Skip to main content
Generic filters
Search in title
Search in content
Search in excerpt
Mono versus .Net Core – Which Platform to Use?
Specialty Level
Background

Related Post

Visual Basic .Net – VB.Net

Mono versus .Net Core – Which Platform to Use?

Do you need to use Mono if you can use .NET Core, and both enable you to run .NET software across different platforms? Whether one “needs” Mono when you can use .NET Core to create software that works on different operating systems and platforms depends on the context and specific project requirements.

Both frameworks serve similar purposes but have different histories, features, and target scenarios.

Here’s a comparative look:  

.NET Core

  1. Cross-Platform: Like Mono, .NET Core is cross-platform and can run on Windows, Linux, and macOS.
  2. Performance: .NET Core has been optimized for performance from the ground up and tends to be more performant than Mono in many scenarios.
  3. Microsoft’s Support: .NET Core is directly backed and developed by Microsoft, ensuring timely updates, security patches, and broad community support.
  4. Unified Platform: With the release of .NET 5, Microsoft has started the journey to unify the .NET platform, making .NET Core, .NET Framework, and Mono features accessible under one umbrella.

Mono

  1. Legacy Projects: If you have older projects built on Mono or are maintaining software that relies on specific features, you might still want or need to use Mono.
  2. Mobile Development with Xamarin: Mono is foundational to Xamarin, which allows the development of mobile apps for iOS and Android using C#. While .NET 5 and later versions have begun integrating mobile development capabilities (thanks to the unification of Mono and .NET Core in the .NET ecosystem), Xamarin’s toolset is mature and widely used in the industry.
  3. Some Platform-Specific Features: Mono has, over the years, developed features and libraries tailored to the platforms it supports. In some edge cases, these features might not be available or directly compatible with .NET Core.  

Conclusion

If you’re starting a new cross-platform project and don’t have a specific reliance on Mono’s unique features, then .NET Core (or .NET 5 and later) is likely the best choice due to its performance, broad support, and Microsoft’s backing. It represents the future direction of .NET development.  

However, if you’re working on a project that already uses Mono or is heavily invested in Xamarin for mobile development, then Mono remains a valid and powerful toolset.

With Microsoft’s efforts to unify the .NET ecosystem, the lines between Mono an