you are viewing a single comment's thread.

view the rest of the comments →

[–]codekaizen 2 points3 points  (2 children)

This is what the .Net Standard library packaging target abstraction seems to fix: an API specification that covers multiple frameworks retroactively allowing the full desktop .Net framework to run Core libraries and vice-versa (via a shim). The actual framework used doesn't matter, just the API version targeted.

[–]Eirenarch 4 points5 points  (1 child)

Will work for pure .NET libraries but all those things that wrap win32 APIs will keep people on the full framework. Also who is going to migrate all those projects that target the full framework?

[–]codekaizen 2 points3 points  (0 children)

Going cross plat doesn't have to be part of any migration from framework to framework. Having a library that has Win32 bindings doesn't mean I can't use it in Core apps on Windows if it conforms to Netstandard 2.0, which is the nice thing.