Use NuGet.Configuration to get the path to the NuGet global… #4301
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… packages folder
refs
#3853
#4209
I don't know the history of things in this area, I just hit #3853 when building some things that use paket on a system that has the
globalPackagesFolder
setting set to a custom location (on a different drive than the default user profile directory) and wondered if it would be possible to fix it by using the 'where is the cache folder' functionality inNuGet.Configuration
rather than doing it locally (it contains the logic to look forNUGET_PACKAGES
, thenglobalPackagesFolder
, then the regular defaults)