Change default .nuget/package folder .NET Core
See original GitHub issueText from documentation:
If not specified, the default NuGet package cache is used. It is found in the .nuget/packages directory in the user's home directory on all operating systems (for example, /home/user1 on Linux or C:\Users\user1 on Windows).
Can I change .nuget/packages location?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Is it possible to change the location of packages for NuGet?
Open %AppData%\NuGet folder, open existing NuGet.Config file. Edit repositoryPath key and set new destination. <config> <add key ...
Read more >Managing the global packages, cache, and temp folders
Starting in Visual Studio 2017, use the Tools > NuGet Package Manager > Package Manager Settings menu command, then select Clear All NuGet...
Read more >Setting the NuGet package folder location for Visual Studio ...
There are two locations for the nuget.config file: in a .nuget folder inside your solution folder and directly in the solution folder (or...
Read more >NuGet - Change the location of the global package cache
By default these packages are stored at the following location: Windows: %userprofile%\.nuget\packages; Mac/Linux: ~/.nuget/packages.
Read more >How To Release a NuGet Package Locally? - Full Duck Dev
Download NuGet.exe from here (latest recommended version is okay) · Place it in a folder it will be stored in. · Copy that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think the NUGET_PACKAGES environment variable might be what you’re after.
Since there was no action here for a while now, I will close this issue. If the problem still repros, please reopen.