4

I'm playing with dotnet-tool and nuget; I noticed that if I push a refresh nameOfPackage.nupkg to the nuget repo and then run dotnet tool update -g nameOfPackage it does not take the new package version.

I have to force a cache clear to get it to take the latest one.

dotnet nuget locals http-cache -c

I previously installed the package doing

dotnet tool update -g nameOfPackage

Is this by design? Do I have to flush the cache every single time to make sure there are no updates to the tool?

1 Answer 1

5

Adding the --no-cache option forces the update.

dotnet tool update -g nameOfPackage --no-cache

enter image description here

Source: dotnet tool update

Sign up to request clarification or add additional context in comments.

1 Comment

I had this issue with GitHub Nuget feed. Somehow the latest version isn't updated. --no-cache helped.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.