'Dotnet tool restore' doesn't update toolResolverCache file

[RomanTimv]

I have two folders. Each folder has dotnet-tools.json and NuGet.config where defined place for packages in the folder.

I call dotnet tool restore from first folder. Package is downloaded into first folder and its path is saved to file in c:\Users<user>.dotnet\toolResolverCache\1\

Then I delete first folder and call dotnet tool restore from second folder. Package is downloaded to second folder, but in toolResolverCache remains path to first folder. Tool can't be runned, it asks for restore.

[dsplaisted]

@wli3 for triage

[wli3]

This is by design. We don't plan to support custom nuget global package folder location (we expect both project would share the same nuget directory). In this case, you can use dotnet tool install --tool-path NAME to achieve better isolation

[RomanTimv]

The issue is if dotnet tool restore doesn't find tool in saved location, it downloads it into another location but tries to run it from saved.

So tool doesn't work if it was somehow deleted from location saved in cache and default location for tools is changed. And only way to restore it is manually delete tool description file from toolResolverCache or part of this file. And it's not obvious solution at all. I had to debug dotnet sources to find out about toolResolverCache folder.

[0x53A]

If this is by design, then your design might not be perfect.

At the least please document these issues in https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file.

We are currently using a globalPackagesFolder inside the repository, and this causes a lot of issues on the buildservers, where multiple builds are running in parallel and the repositories are in randomized locations.

After learning about this, I'll try to rework our build to no longer set globalPackagesFolder.

[sliekens]

This is also a problem when you use the machine-wide NUGET_PACKAGES environment variable.

Repro steps on Windows using command prompt:

1. mkdir repro
2. cd repro
3. dotnet new tool-manifest
4. set NUGET_PACKAGES=%cd%\packages
5. dotnet tool install dotnetsay
6. dotnet dotnetsay ok should work correctly
7. dotnet nuget locals global-packages --clear
8. set NUGET_PACKAGES=%cd%\packages2
9. dotnet tool restore downloads the tool again to packages2
10. dotnet dotnetsay fails because toolResolverCache is not updated

Deleting the toolResolverCache folder is the only way to make the tool work again.

Sorry, but this cannot be by design, rather lack thereof.