You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My machine is configured in %APPDATA%\NuGet\NuGet.Config to use D:\cache\.nuget for the cache location, and I have Windows Deny ACLs enabled on %USERPROFILE%\.nuget to force tools to fail if they incorrectly determine it is acceptable to write data to this location. This is causing Arcade repositories to fail to build without modifying their build scripts to correct the hard-coded locations.
Side note: I use Deny ACLs in many locations as part of validating various products and tools don't make incorrect assumptions that may not hold on end user machines (e.g. telemetry caches on disk should not be used when telemetry reporting is disabled), so this is standard practice and severely impairs my workflow until fixed.
The text was updated successfully, but these errors were encountered:
Make sure to account for per-user NuGet.Config as a way to configure the
location of the global packages cache. Avoid setting NuGetPackageRoot in
RepoLayout.props because it is already being set to the correct location
in the *.nuget.g.props files created for each project.
Fixesdotnet#14761
The following line incorrectly assumes that NuGet cache location is only configured by the NUGET_PACKAGES environment variable:
arcade/eng/common/tools.ps1
Line 645 in a62b463
The script further incorrectly assumes that the default cache location when NUGET_PACKAGES is not defined:
arcade/eng/common/tools.ps1
Line 651 in a62b463
My machine is configured in
%APPDATA%\NuGet\NuGet.Config
to useD:\cache\.nuget
for the cache location, and I have Windows Deny ACLs enabled on%USERPROFILE%\.nuget
to force tools to fail if they incorrectly determine it is acceptable to write data to this location. This is causing Arcade repositories to fail to build without modifying their build scripts to correct the hard-coded locations.Side note: I use Deny ACLs in many locations as part of validating various products and tools don't make incorrect assumptions that may not hold on end user machines (e.g. telemetry caches on disk should not be used when telemetry reporting is disabled), so this is standard practice and severely impairs my workflow until fixed.
The text was updated successfully, but these errors were encountered: