A couple of weeks, I told you about NuGet Package Source Discovery. In short, it allows you to add some meta information to your website and use your website as a discovery document for NuGet feeds. And thanks to a contribution to the spec by Marcin from SymbolSource.org, Package Source Discovery (PSD) now supports configuring Visual Studio for consuming symbols as well. Nifty!
Let’s go with an example. If we discover packages from my blog, some feeds will be added to NuGet in Visual Studio.
1 Install-Package DiscoverPackageSources 2 Discover-PackageSources -Url ""
Because my blog links to my feeds on MyGet, I can provide my MyGet credentials with it:
1 Install-Package DiscoverPackageSources 2 Discover-PackageSources -Url "" -Username maarten -Password s3cr3t
Note I’ve stripped out some of the secrets in the examples but I’m sure you get the idea.
What’s interesting is that because I provided credentials, MyGet also returned the SymbolSource URL for my feeds and it registered them automatically in Visual Studio.
Now that’s what I call being lazy in a professional manner!
On a side note… NuGet Feed Discovery
While not completely related to SymbolSource support, it’s worth mentioning that Package Source Discovery also got support for that other NuGet discovery protocol by the guys at Inedo, NuGet Feed Discovery (NFD). NFD differs from PSD in that both specs have a different intent.
- NFD is a convention-based API endpoint for listing feeds on a server
- PSD is a means of discovering feeds from any URL given
The fun thing is: if you add an NFD url to your web site’s metadata, it will also be added into Visual Studio by using NuGet Package Source Discovery. For reference, here’s an example where I add my local NuGet feeds to my blog for discovery:
1 <link rel="nuget" 2 type="application/atom+xml" 3 title="Local feeds" 4 href="http://localhost:8888/nugetext/discover-feeds" />
This is an imported post. It was imported from my old blog using an automated tool and may contain formatting errors and/or broken images.