That’s the same as File -> New as what I referred to below. What likely happened was that NuGet had cached the previous version of your “invalid” package and never picked up the new package. Change the version every build to avoid that (such as va Nerdbank.GitVersioning).
From: ozdotnet-boun...@ozdotnet.com <ozdotnet-boun...@ozdotnet.com> On Behalf Of Greg Keogh Sent: Wednesday, April 22, 2020 12:16 PM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: Re: Nuspec file for netstandard2.0 FYI for newer SDK-style projects, dotnet pack may work better than nuget.exe if you're at the command-line Oh yeah!! Thanks for reminding me. I use .NET Framework and nuge.exe 95% of the time at the moment, and I forget that dotnet pack should be used for certain project types. Maybe that explains some of my befuddlement in previous days. I'll run some experiments -- Greg
