Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
NuGet - Manage Solution Packages Major Improvements Needed #7595
Sorry if my title offends, but simply stated: the NuGet UI is terrible when it comes to assigning multiple packages to multiple solution projects. In my case I have a solution with 30 projects and a total of about 100 individual packages, I have to manually go through each package, apply them and try to remember where I was last because the UI refreshes and losses the selected package I just applied. Furthermore, the scrolling is aweful. You have to arrow up or down to know where you are because many of the package names are similar and tend to blur toghether. I recomend an option to hide the description (because we don't alway need to see it), and just show the title plus the created-by value.
Another suggestion is: how about a bulk update option (like how a shopping cart works for a web-site). In my case I have so many updates to make and it would be nice if I can queue all my udpates (accross packages and projects), until I'm done and apply them in sequence.
Lastely: It sucks that the update fails to checkout certain files. For example, if you have a .NET Standar 1.4 project under source control, and try to apply a package, the UI fails saying "Access denied when writting to ...<path>\project.json". I have to checkout all project.json files and try my update again. It would be nice if this UI would check-out the file AND if it could hold my changes until I address the issue. By "hold my changes" I mean the bulk update if that feature is added.
This issue has been moved from https://developercommunity.visualstudio.com/content/problem/72532/nuget-manage-solution-packages-sucks.html
ahenderson on 8/6/2017, 10:31 PM (485 days ago):
I'm also on VS2017 and agree 100% that the whole nuget package manager GUI is rubbish. It appears people have been complaining about this since VS2015 was released and nothing has changed. I hold little hope that this will be fixed and plan to learn the console instead.
Major irritations for me:
Background threads update ui elements at arbitrary times, changing things like version numbers etc. This is a usability nightmare, stop doing this!
What is the current installed version of a package? Why do I even need to ask this question? It is just unbelievable that a package manager doesn't make this obvious.
The version number displayed next to the package name in the installed tab, seems to flip between the latest version available, nothing, and the installed version.
I hope whoever designed this no longer works for Microsoft.
Cameron Miller on 12/2/2018, 05:25 PM (2 days ago): I dislike how long it takes to display the packages on the Installed, Updates and Consolidate tabs. Particularly why does it always refresh when clicking between tabs? Why can't it cache information and provide an optional force refresh or refresh on change (or apply change queue)?I dislike the "Include prerelease" checkbox. Its presence on a the Installed tab is confusing. It is confusing to have different behaviour depending on the tab context (on the browse and updates tab it filters out the packages in the list; on the installed, updates tab it changes the right-hand check-list to show Updates. When using pre-release pacakges seeing the Include preprelease is confusing: will it show my installed prerelease package? It is a little confusing to see updates on an installed tab. Particularly the version in the right column of the left pane. It can show the next version, when it definitely should be showing the installed version - That's actually a bug!Why can't the consolidate tab allow multiple actions in on request like the updates tab?