.NET runs natively on Linux since quite some time. Honestly, I don’t get what Mono is even good for these days. Maybe reverse engineering old .NET versions.
.net core is the future but Mono is still important for running legacy .net framework applications like ones that use WinForms or WPF. That’s pretty much it. Anything new should go straight to .net core.
When I moved my personal laptop to Linux I needed WINE to run some source-available .NET apps that were written targeting the Windows-only .NET Framework
.NET runs natively on Linux since quite some time. Honestly, I don’t get what Mono is even good for these days. Maybe reverse engineering old .NET versions.
.net core is the future but Mono is still important for running legacy .net framework applications like ones that use WinForms or WPF. That’s pretty much it. Anything new should go straight to .net core.
Hm, WinForms and WPF with Wine you mean? Otherwise makes not much sense. Was WPF ever run in this combination!
Ah yeah. Mono didn’t support WPF, but Mono did support running WinForms apps natively on Linux without using Wine.
The problem with WinForms is that at least serious 3rd party libraries do a lot of direct API calls I guess, hence Wine.
Only
.NET CoresadlyWhen I moved my personal laptop to Linux I needed WINE to run some source-available .NET apps that were written targeting the Windows-only
.NET FrameworkAll the new stuff is now on .NET Core/5.0 and up at least.
Hasn’t been called “.NET Core” since 3.1
Although it’s essentially the subsequent version of core, .NET 5 is the successor to both .NET Core 3.1 and .NET Framework 4.
Since then, it’s just been called .NET 5/6/7/8/…
IIRC Mono was mostly used for WASM as it was optimized for smaller builds than the full fat CoreCLR (talking about .NET non-Framework Mono)
WASM? Are you talking about WebAssembly?
yes