Portable vs .NET Standard about musicbrainz

[wo80]

Portable class libraries were a first approach to open .NET to other platforms/devices (like Windows Phone - there never was a full .NET framework for Windows Phone).

The whole idea of portable projects was indeed confusing and is now replaced by the .NET Standard (which is a good thing imho).

More info:
https://stackoverflow.com/questions/5238955/what-is-a-portable-class-library
https://www.infoq.com/news/2017/10/dotnet-core-standard-difference

[ColorTwist]

From what i read .NET Standard 2.0 is the way to go. Like you said.

[wo80]

Here's one problem I see:
Portable class libraries are supported since VS2010, while support for .NET Standard projects is only there since VS2017.

If this isn't a problem, then the whole solution could be re-organized:
http://markheath.net/post/supporting-net-standard-and-net-35
https://docs.microsoft.com/en-us/dotnet/core/porting/

This would also simplify the creation of the nuget package.

[ColorTwist]

Never used it, just made me confused. Why does someone needs the portable version?

[ColorTwist]

It is evolving, final stages of being released 2.1 core.
https://blogs.msdn.microsoft.com/dotnet/2018/04/18/performance-improvements-in-net-core-2-1

[ColorTwist]

Personally i use VS2017.
VS2017 is available from March 2017. I guess many have updated.