Remove a package from visual studio marketplace

We'd probably all be better off if the Package Manager UI was removed and we were forced to use the command-line, at least that way the command-line UX would - You mentioned the one filename that will make the nuget team will completely disregard and ignore your entire post.

And this atrocious UI has been around for over 5-6 years now with no improvement. We'd probably all be better off if the Package Manager UI was removed and we were forced to use the command-line, at least that way the command-line UX would improve.ДЄlso, why on earth is the visual NuGet Package Manager UI seemingly so inefficient? Why can't it read all of my nfig files and display that information instantly and then load data from the Internet? And why does it have to reload everything whenever I make even the smallest change? I especially dislike how I have to manually scroll to the bottom of the list for the UI to load the rest of the items. Related-but-unrelated rant:ДЄlso, why on earth is the visual NuGet Package Manager UI seemingly so inefficient? Why can't it read all of my nfig files and display that information instantly and then load data from the Internet? And why does it have to reload everything whenever I make even the smallest change? I especially dislike how I have to manually scroll to the bottom of the list for the UI to load the rest of the items. I need to invoice Microsoft for my blood-pressure medication. I actually (yes, literally) feel a spasm of pain every time I get the red error messages from the package-manager console because every time I see it it's because it rejected a command that a reasonably intelligent tool should be be able carry-out - it's the same kind of frustration you get when you deal with unhelpful customer service: you know they can do something, but it isn't because management/policy/Microsoft decided not to for some undefined, unexplained reason.

What I thought would be a 30-second single command-line or GUI operation has turned into a 30-minute exercise in pain. Uninstall-Package : Unable to uninstall 'System.Memory.4.5.3' because '.2.2.0, .1.7.0, .4.7.0' depend on it.ДЄt this point I had to manually copy+paste the dependency lists for all of the Microsoft.ApplicationInsights.* packages to a spreadsheet (to keep track of them all) and remove them manually, one-by-one by doing the dependency-walking manually by hand. Resolving actions to uninstall package '.2.12.0' PM> Uninstall-Package -RemoveDependenciesД®rror (because the package is already removed):ДЄttempting to gather dependency information for package '.2.12.0' with respect to project 'OhGodEverythingIsTerrible', targeting '.NETFramework,Version=v4.7.2' 'Okay, let's re-run the command with -RemoveDependencies.' This worked - but it only removed - all of the other Microsoft.ApplicationInsights.* package references are left behind and now orphaned, so tooling can't see that they were only referenced because depended on them.People have to write their own programs just to get a dependency graph, which is ridiculous. I note that this assumes you know which package is the real 'root' package - which none of the built-in tooling will tell you.let's try removing the platform-specific Application Insights package instead' 'hmm, that didn't make any difference at all. Resolving actions to uninstall package 'Microsoft.ApplicationInsights.2.12.0' Attempting to gather dependency information for package 'Microsoft.ApplicationInsights.2.12.0' with respect to project 'OhGodEverythingIsTerrible', targeting '.NETFramework,Version=v4.7.2'

Remove a package from visual studio marketplace