The first step involves upgrading to the new csproj format. We're starting off with a Visual Studio 2015 solution and an old csproj file. We'll be using Visual Studio 2017, and my Blazer library as a working example. NET platforms from a single Visual Studio project. There is some documentation, but it's all scattered information that fails to paint the full picture. However, exactly how to create such a package (including setting up Visual Studio) is never fully described. NuGet has supported placing multiple versions of the same library in one package for quite a while now. NET Standard, while also remaining compatible with version 4.5 of the full.
I now want to target multiple platforms: I want to target. However, this only covered the basic scenario of targeting a single platform. In a previous post, I showed how to create and publish a simple NuGet package.
NET Standard, in order to make my package available on a wider variety of platforms. As the proud owner of a NuGet package (72 downloads and counting!), I'm interested in targeting the new.
