.NET 5

[woohoo]

It gets better. .Net Core (now .Net 5) includes almost everything that was in .Net Framework, including stuff that is not cross platform compatible, which was the original goal of .Net Core.

e.g. They've included WinForms as many still prefer that over the ever changing WPF/UWP 'modern' alternatives M$ keep sicking up.

Work wise, the .Net gravy train just got a new lick of paint.

My understanding is .Net Core is cross platform compatible, but some features that use it are not. Like WinForms/WPF. They have just bundled it together along with other things. I'm not going to try and use WinForms on MacOS because it's never going to work in a million years, but I can use WinForms on Windows and WinForms uses .Net Core.

That's my understand and seems straightforward (until someone points out I'm wrong .

[dx4100]

Work wise, the .Net gravy train just got a new lick of paint.

The only quote on this thread which counts

[Hobosapien]

My understanding is .Net Core is cross platform compatible, but some features that use it are not. Like WinForms/WPF. They have just bundled it together along with other things. I'm not going to try and use WinForms on MacOS because it's never going to work in a million years, but I can use WinForms on Windows and WinForms uses .Net Core.

That's my understand and seems straightforward (until someone points out I'm wrong .

Logically it makes sense to have one .Net framework for all the things they want to support going forwards but in a library that is cross platform capable even if all features aren't.

So rather than something new it's just .Net Framework without the bits they want to drop (WebForms, WCF, WWF, ... and VB.Net which is included but deprecated) and they've made it usable on non-Windows to appeal to those wanting to avoid Windows Server for hosting and cloud. Meh, where's the real innovation.

[d000hg]

OK so basically .Net5 is .Net but they switched in the open-source stuff... they've managed to converge things back together.

[NigelJK]

UWP