4 ms·
Suggested naming standard: - .Net API Specification - (now known as .Net Standard) - .Net Windows - (now known as .Net Framework) - .Net Cross Platform - (no
by stevecalifornia 8y ago
Suggested naming standard:
- .Net API Specification - (now known as .Net Standard)
- .Net Windows - (now known as .Net Framework)
- .Net Cross Platform - (now known as .Net Core)
- sebazzz 8y agoI don't think Microsoft is going to rename .NET Framework, that would already break too much for too little benefit. .NET Core would simply not be renamed because it is too well known. Regarding ".NET Standard", I agree, it is an API specification but to prevent confusion you should think (for now) of it as "The .NET Standard [API set]".
- paulddraper 8y agoYou're right of course, but it's a crying shame that it's so unobvious what things are.
- blinkingled 8y ago.NET XP sounds better for .Net Core :)
- ctrl-j 8y agoFor Windows XP?
- blinkingled 8y agoSince nobody uses Windows XP anymore that should not be so confusing.
- legulere 8y agoThere’s already universal windows platform, which is basically windows 10 only.
- mbesto 8y agoKnowing the differences here is pretty serious for my day-to-day work. Does anyone have a guide/breakdown/etc that I can refer to that explains all of the versions of .NET? The documentation from Microsoft itself is atrocious. Does it exist somewhere?
- pjmlp 8y agoNot a breakdown, but here goes. https://docs.microsoft.com/en-us/dotnet/framework/whats-new/ https://docs.microsoft.com/en-us/dotnet/framework/whats-new/ Only goes down to 4.5, as older versions are already EOL. The archived MSDN docs do have the older versions in case you are interested. Which runtimes implement which versions of .NET Standard: https://docs.microsoft.com/en-us/dotnet/standard/net-standard https://docs.microsoft.com/en-us/dotnet/standard/net-standar...
- oaiey 8y agoI think .NET Standard is quite right. It is a" standard". And standards rarely have implementations on their own.