I recently tried out Dev Drive of Windows 11, where a ReFS partition can be created for your code and packages. It went smoothly and most of my projects were built successfully until it came to my Monogame project.
For your context, Monogame is a game engine written in .NET and allows you to write your game entirely in C#. It has a content pipeline to convert your audio and images assets to certain format, and the pipeline is written as local dotnet tools.
Turns out dotnet tools stop working after I moved Nuget package cache folder to the Dev Drive (with NUGET_PACKAGES environment variable). I tried to trigger the tool manually, but the error message is confusing an unhelpful:
|
1 2 3 4 5 6 7 |
❯ dotnet mgcb Run "dotnet tool restore" to make the "mgcb" command available. ❯ dotnet tool restore Skipping NuGet package signature verification. Tool 'dotnet-mgcb' (version '3.8.1.303') was restored. Available commands: mgcb ❯ dotnet mgcb Run "dotnet tool restore" to make the "mgcb" command available. |
I tried to check my Dev Drive and I can see dotnet-mgcb had been restored correctly. Looking a bit further, I realized that .NET is still trying to look for the tool in the old path in %userprofile%\.nuget (even after computer restart).
I might have guessed the issue by now: there must be a cache somewhere pointing to the old paths. Turned out local dotnet tools cache the package information (including the path) in %userprofile%\.dotnet\toolResolverCache.
The fix is obvious now:
- Empty
%userprofile%\.dotnet\toolResolverCache - Run
dotnet tool restoreagain and double check toolResolverCache to ensure the files are recreated.
I think ideally, since dotnet tool restore can already get the package to the new cache folder in Dev Drive, it should also try to update this toolResolverCache folder automatically instead of requiring a manual wipe like this.