You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful to pass the --force flag to nuget restore in order to bypass the noop cache of nuget so that scripts will check for a newer version of a package each time they are run, when wildcards are used that end up in the PackageReference. This could be by argument or convention, or by default when --no-cache is specified (which it seems it not passed through to nuget restore in DotnetRestorer.cs?) - whatever you think is right for your project :)
Currently am running dotnet nuget locals --clear all before running such scripts - and this takes a long time when the .nuget cache is big (which it usually is!)
The text was updated successfully, but these errors were encountered:
See NuGet/Home#5445
It would be helpful to pass the --force flag to nuget restore in order to bypass the noop cache of nuget so that scripts will check for a newer version of a package each time they are run, when wildcards are used that end up in the PackageReference. This could be by argument or convention, or by default when --no-cache is specified (which it seems it not passed through to nuget restore in
DotnetRestorer.cs
?) - whatever you think is right for your project :)Currently am running dotnet nuget locals --clear all before running such scripts - and this takes a long time when the .nuget cache is big (which it usually is!)
The text was updated successfully, but these errors were encountered: