What issue are .NET Standard and .NET Core intended to solve? -
i've read things .net standard , .net core, , seem "this new way things, , here advantages , disadvantages."
what haven't seen good, clear explanation of wrong status quo, such .net standard , .net core necessarily. judge should use these for, helpful know why exist @ all.
can give clear (and not concise!) explanation of (a) problem .net standard , .net core intended solve, , (b) how solve it?
.net standard set of library contracts. each version includes contracts of previous version - in netstandard1.4 in netstandard1.5 example.
.net core implementation of .net standard (and functionality) runs on windows, linux , osx.
biggest problems solve:
- not having microsoft-provided/supported toolchain , runtime on linux/macosx. saying run .net-based server code on windows or mono untenable.
- the portable class library mess hundreds of different profiles giving partially-overlapping api surfaces target.
pcls in particular hard work class library authors such myself. mess came because there multiple efforts bring .net runtime different devices without enough coordination provide coherent api surface target.
now multiple vendors can target particular versions of .net standard, , targeted version or higher should work. example, noda time library targets netstandard1.3. suppose new mobile phone vendor comes out new implementation of .net, new kind of application - says support netstandard2.0. that's fine - user of new platform still able install noda time nuget package , (implementation bugs aside, of course) they'll able use it. don't need know platform exists.
Comments
Post a Comment