-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NuGet locals command should allow deleting specific packages from NuGet global packages folder #5713
Comments
cc @emgarten The following seem like repeated asks:
In the 2nd case it clears all packages that are directly referenced in the project. |
Looks very useful. It would also be nice to prune everything not in a solution, or older than a certain time. |
This win my vote. It should be very useful to remove older packages than just clear all of global cache. |
@SupporterMan @neolib Thanks for reporting this request. We will consider this request, when possible. |
Could really do with |
There are news around this? |
Deleting specific packages from the NuGet global packages folder will improve the inner-loop development of a NuGet package on the local machine. But this issue has been open since 2017, so in the meantime I created a solution to address this problem. I recently decided to make my solution public by releasing a package called NuJet (https://github.com/gioce90/NuJet). It enhances the inner-loop development and testing process for NuGet packages, especially in local workflows. Feel free to check it out—I’d love to hear your feedback! |
Details about Problem
I have a nuget package that want to remove it from my project and I also want to clear its local global cache from userprofile.nuget\package. According to the manage package document, I only could use "nuget locals global-packages -clear" command to clear all global caches, not a specific one. Otherwise, I need to navigate to the .nuget\packages path in file folder and delete it manually.
NuGet product used: NuGet.exe
NuGet version (4.1.0)
edit by @nkolev92
This issue should cover the VS side of things as well. #8204
The text was updated successfully, but these errors were encountered: