Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nuget reference with * v.s. the nuget NoOp cache #541

Open
dave-yotta opened this issue Jun 2, 2020 · 0 comments
Open

nuget reference with * v.s. the nuget NoOp cache #541

dave-yotta opened this issue Jun 2, 2020 · 0 comments

Comments

@dave-yotta
Copy link

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!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant