> File -> New -> .NET Standard project -> right-click project and choose > Pack. >
I tried that very early on. It produces a package which looks okay, it has Dependenies .NETStandard,Version=v2.0 for the two Google packages I expect, and it has two correct files in the lib\netstandard2.0 folder. However, when I install the package into a .NET Core 3.1 command prompt test project it installs no dependencies, only the lib contents arrive. I tried another netstandrd2.0 project as the target and it makes no difference. I stole the contents of that generated nuspec and modified it in a hundred ways to customise it the way I want (you only have basic package configuration in the VS2019 project properties). Nuget 5.5.1 pack always gives NU5128 (but I can't fix that and I ignore it) and I get a package which has Dependencies Unsupported, Version=v0.0 and it also installs no dependencies at the target. The fact that the VS2019 pack generated package will not install is really suspicious. The fact that I can't generate a valid looking package is a separate problem. This is really bad. I'm getting inconsistent results and none of them install correctly. Either I'm using the wrong tools, I'm on the wrong platform or it's time for me to throw in the towel and retire. I have a quiet morning, so I'll spend another 3 hours on this, then consider retirement. *Greg K* P.S. For years NuGet used to just work, but it looks like the introduction of the different platform support has thrown a spanner in the works and it's become a jumble full of quirks and traps. And the documentation is appalling.
