Will .Net Framework projects become Cross-Platform by .Net 5

user_1862658 0
Viewed 390

Scott announced tat the next version of .Net Core and .Net framework will be released and unified as .Net 5 in November 2020 just few months later.

So we have decided to port some of our projects into .Net Core such as our WCF services and so on but based on these sentences from here.

.NET Framework 4.8 will be the last major version of .NET Framework. If you have existing .NET Framework applications that you are maintaining, there is no need to move these applications to .NET Core. We will continue to both service and support .NET Framework, which includes bug–, reliability– and security fixes. It will continue to ship with Windows (much of Windows depends on .NET Framework) and we will continue to improve the tooling support for .NET in Visual Studio (Visual Studio is written on .NET Framework).

There will be just one .NET going forward, and you will be able to use it to target Windows, Linux, macOS, iOS, Android, tvOS, watchOS and WebAssembly and more.

what does the real meaning by If you have existing .NET Framework applications that you are maintaining, there is no need to move these applications to .NET Core.
One of major gain for us by porting .Net Framework application to .Net Core is being Cross-Platform.

.net-5 .net-core .net
2 Answers

All they are saying there is that nobody is coming to uninstall .NET Framework from their machines; whatever works today, will keep working. This is to stave off cries of "you broke our perfectly working system" and people fetching pitch-forks.

All of the benefits, including (but not limited to) cross-platform compatibility: are in .NET Core, and it is absolutely correct to migrate to .NET Core if you even possibly can.

Marc_Gravell_233540

You will get 10 years of support with what came native to that platform. The newest is Windows Server 2019 and it had 4.7.2 native. 4.7.2 should be "in support" until 2029.

user_38177090
Related