LINQPad doesn't use nuget package cache in NUGET_PACKAGES environment variable
I have two users on a server and I've set the NUGET_PACKAGES environment variable to point to a folder (D:\nuget\packages). I've tried it as a permanent variable for each user via setx and as a system environment variable. One user uses that folder as the local package cache and the other one doesn't. The one that doesn't reverts back to the usual APPDATA location. I've checked that the user has permission to access the folder. How can I troubleshoot this? Is there any log indicating how LINQPad selects the folder to use and why it's having trouble using the one from the environment variable?
Nuget itself seems to report the correct location for both users:
C:\Users\afrancis>dotnet nuget locals all --list http-cache: C:\Users\afrancis\AppData\Local\NuGet\v3-cache global-packages: D:\nuget\packages temp: C:\Users\afrancis\AppData\Local\Temp\2\NuGetScratch plugins-cache: C:\Users\afrancis\AppData\Local\NuGet\plugins-cache
Is there any difference in the NuGet.config files?
Hi Joe, the two files were identical. It doesn't seem like it's a problem with LINQPad. I ended up reinstalling LINQPad, clearing the cache, setting the globalPackagesFolder setting in NuGet.config and reinstalling the packages as the second user. One of these steps fixed the issue and now both users can see the same packages.