I want to chime in on this suggestion from Peter:
“It would be nice to have a link to the nuget.org page for the package (where applicable). I don't expect to do everything from the Package Manager, but it would be nice to quickly jump to nuget.org to do infrequent tasks like report a package or
Please note that a package can be installed/restored from other repositories as well (eg. myget.org), or even from an aggregate feed that has multiple upstream package sources.
There’s currently no link whatsoever between an installed package and the repository it originates from, and I’m not sure it’s a good idea to try to keep track of something this dynamic on the client (eg. in the case of feed aggregation, the client shouldn’t
know or care which upstream package source actually contained the package, that’s the whole point of aggregation).
The only thing the UI can rely on imho is the package metadata contained within the package (eg. licenseUrl and projectUrl). This also ensures that all feed hosts can provide the same information.
If a link to nuget.org is to be exposed in the UI, I believe the same should be possible for other package repositories (some enterprises will only use internal feeds btw, in which case that link should point to their own repository instead of nuget.org).
This is also a VisualStudio specific thing, so it could make sense to expand on the “Add Package Source” UI in the Visual Studio options (and while at it, it would be
if one could simply point to a feed endpoint and have the server populate the other fields for the end-user.).