"no-cache" option for dotnet tool update

Steps to reproduce

I created a tool which I uploaded to a private nuget server. I did an install, and then created an update (0.0.2).

Expected behavior

dotnet tool update updates to 0.0.2

Actual behavior

However, once I posted this to the nuget server, I could not update it through the dotnet tool update, it still gave me 0.0.1. I am sure 0.0.2 was visible as when I did check it through Visual Studio the nuget installer gave me 0.0.2. But through the dotnet tool update it sill gave me 0.0.1. An half hour later, I was able to get 0.0.2.

So question is, is there a caching mechanism into the dotnet tool verb? And also, why not use the nuget installed sources for resolving, caching etc? Now we have to give --add-source for example …

[NickLydon]

The --no-cache flag doesn’t seem to do anything for me when running dotnet tool install. I’m developing a tool locally, and it always adds the package to C:\Users\n.lydon.nuget\packages. I need to delete it from the cache every time I make changes and want to re-install.

[SamJ26]

dotnet tool install --no-cache does not work for me and it still uses cached .dlls. The only workaround when testing new dotnet tools locally is changing versions every time I do dotnet pack.