As of version 3.0, WinForms and WPF is also supported by.Dotnet-Core did not come with WinForms or WPF or anything like that. And while the SDK supports multiple OS, ARM support for the SDK is/was still work in progress.NET Core is supported by Microsoft. NET Core runtime supports multiple operating systems and processors, the SDK is a different story. NET framework the sysadmin has actually installed. On the one hand, this means docker.io support on Linux, and on the other, self-contained deployment is useful in 'cloud-computing', since then you can just use whatever version of the dotnet-CORE framework you like, and you don't have to worry about which version(s) of the. NET framework/VM installed on the target machine. NET Core, apart from multi-platform support, is to improve performance, and to enable 'native compilation'/self-contained-deployment (so you don't need. NET Framework will go the way of the Dodo/Silverlight/WindowsPhone. NET Framework 4.8.x for a few decades, until it will die (maybe there are still going to be some upgrades, but I doubt it). NET Framework will linger around in maintenance mode as Full. NET 5.0 without the 'Core', and that then will be the future of the.

NET Core will jump to version 5.0, be known as. NET Core, so much so that after version 3.1. (Since it's Turing-complete and supports interop with C dlls, you could, if you absolutely wanted to, also write your own desktop applications with it, for example through 3rd-party libraries like Avalonia, which were a bit very basic at the time I first wrote this, which meant you were pretty much limited to web or server stuff.) Over time, many APIs have been added to. It started for most part with a re-write of the ASP.NET MVC framework and console applications, which of course includes server applications. NET Core now officially is the future of.

Mono framework design