The first problem is that .NET Standard is not a specification in a traditional sense: "The official spec is a set of .cs files that define the APIs that are pa

The first problem is that .NET Standard is not a specification in a traditional sense: "The official spec is a set of .cs files that define the APIs that are part of the standard." [0] If you're new to the .NET ecosystem and you try to dig deeper, you find yourself having to understand more and more things: .NET Core, project.json (dependencies, frameworks, imports), vNext, portable class library, PCL profiles, CLI implementations etc, all the while battling misinformation, confusion and terrible proprietary tools, should you chose (or be forced to!) use them. It took me about two weeks to finally wrap my head around the ecosystem in an effort to build a ".NET Standard library"(not a standard library) with a few dependencies and use it in a non-trivial Xamarin project. Let me know if you'd like me to share. [0] https://docs.microsoft.com/en-us/dotnet/articles/standard/library#specification https://docs.microsoft.com/en-us/dotnet/articles/standard/li...