.NET Standard 2.0 is final
github.com
.NET Standard 2.0 is final
1–10 of 69 posts
Re: .NET Standard 2.0 is final
#2Such a confusing name. I thought this was the .NET Spec publication. Still better than .NET 365 Premium Plus I guess :-)
Re: .NET Standard 2.0 is final
#3Such a confusing name. I thought this was the .NET Spec publication. Still better than .NET 365 Premium Plus I guess :-)
I think it is the spec? I don't blame you for the confusion though.
I do think that there is light at the end of the tunnel and that once Microsoft finally works through all this, it will be a lot less confusing. But lord has it been a painful transition. My head is swimming in ".NET "s
Re: .NET Standard 2.0 is final
#4Such a confusing name. I thought this was the .NET Spec publication. Still better than .NET 365 Premium Plus I guess :-)
".NET Standard is a specification that represents a set of APIs that all .NET platforms have to implement. This unifies the .NET platforms and prevents future fragmentation. Think of .NET Standard as POSIX for .NET."
Re: .NET Standard 2.0 is final
#5Compatibility mode sounds like a godsend for those of us who have had to hold back due to compatibility issues with third party code/libraries. It's a risk, to be sure, but awesome that it's an option now.
Side note: very much looking forward to UWP targeting .NET standard. Not long now before you'll be able to develop UWP apps for Ubuntu and Mac OS :)
Re: .NET Standard 2.0 is final
#6Does anybody have any idea what is the total number of APIs available in .NET Framework? I am interested how big of a subset .NET Standard is.
Re: .NET Standard 2.0 is final
#7Such a confusing name. I thought this was the .NET Spec publication. Still better than .NET 365 Premium Plus I guess :-)
The ".NET Spec" doesn't have the name ".NET" in it anywhere - .NET has always been the name of Microsoft's implementation of the Common Language Infrastructure spec (https://www.ecma-international.org/publications/standards/Ec...).
Now that Microsoft itself (and Mono + Xamarin) has multiple implementations of the CLI, it's spec'd the API surface area that is to be expected across the multiple implementations (since this is explicitly not covered in detail in ECMA335) - hence the name, .NET Standard.
Re: .NET Standard 2.0 is final
#8Heh, .Net Contracts is in there. I thought that was basically unmaintained.
Re: .NET Standard 2.0 is final
#9I don't really get what the purpose of this spec is. I would much prefer if they spent the time on improving the .NET Core story. In typical MS manner .NET seems to get more confusing all the time.
Re: .NET Standard 2.0 is final
#10Does anybody have any idea what is the total number of APIs available in .NET Framework? I am interested how big of a subset .NET Standard is.
Apparently ~70% of current nugets are compatible with the standard, which I thought was interesting.