Some companies restrict which third-party libraries their developers may use. Therefore, they might not want developers to have access to everything in the official NuGet feed, or they might have a set of proprietary libraries they want to make available in addition to the official feed.
In these scenarios, you can set up a custom NuGet feed, and you can configure Visual Studio to offer that feed instead of or in addition to the official feed. A feed can be local (a folder on the local machine or a network folder) or remote (an internet URL).
Begin by creating or getting the packages you want to include in the custom feed and then putting them all into a folder. In the following example, a folder has been created in the local c: drive. The folder contains a single package (.nupkg file).
Next, specify that folder as the location of a NuGet feed. In Visual Studio, from the Tools menu select Library Package Manager and then click Package Manager Settings.
The Options dialog box is displayed.
In the Name box, enter a name for your feed. In the Source box enter the path of your packages folder.
Click Add. Your local folder is now another NuGet feed source.
To install a package using the new feed, in the Package Manager Console window, select the new feed in the Package source list.
You can also select the new feed in the Online tab of the Manage NuGet Packages dialog box.
You can also host a remote (or internal) feed on a server that runs IIS.
Make sure you're running NuGet 1.4 or higher!
Go to the File | New | Project menu option (or just hit CTRL + SHIFT + N) which will bring up the new project dialog and select ASP.NET Empty Web Application as in the following screenshot.
This results in a very empty project template.
Now right click on the References node and select Manage NuGet Packages to launch
the NuGet dialog (alternatively, you can use the Package Manager Console instead and
Click the Online tab and then type NuGet.Server in the top right search box. Click Install on the NuGet.Server package as shown in the following image.
NuGet.Server 1.5, you can configure the folder which contains your packages. The web.config file contains a new
packagesPath. When the key is omitted or left blank, the packages folder is the default ~/Packages. You can specify an absolute path, or a virtual path.
<appSettings> <!-- Set the value here to specify your custom packages folder. --> <add key="packagesPath" value="C:\MyPackages" /> </appSettings>
That's it! The NuGet.Server package just converted your empty website into a site that's ready to serve up the OData package feed. Just add packages into the Packages folder and they'll show up.
In the following screenshot, you can see that I've manually added a few packages to the default Packages folder.
If you want these packages to be published (such as when selecting Build -> Publish from the application menu) you'll also need to select the .nupkg files in Solution Explorer and change the Build Action property to "Content".
NuGet.Server 1.4, you can also add and delete packages to the lightweight feed using
NuGet.exe. After installing the package, the web.config file will contain a new
apiKey. When the key is omitted or left blank, pushing packages to the feed is disabled. Setting the
apiKey to a value (ideally a strong password) enables pushing packages using NuGet.exe.
<appSettings> <!-- Determines if an Api Key is required to push\delete packages from the server. --> <add key="requireApiKey" value="true" /> <!-- Set the value here to allow people to push/delete packages from the server. NOTE: This is a shared key (password) for all users. --> <add key="apiKey" value="" /> </appSettings>
If however your server is already secured and \ or you do not require an api key to perform this operation, set the requireApiKey value to false.
I can hit CTRL + F5 to run the site and it'll provide some instructions on what to do next.
Clicking on "here" shows the OData over ATOM feed of packages.
Now all I need to do is deploy this website as I would any other site and then I can click the Settings button and add this feed to my set of package sources as in the following screenshot.
Note that the URL you need to put in is http://yourdomain/nuget/ depending on how you deploy the site.
Yes, it's that easy! An alternative way of publishing packages to this server is by simply placing the nupkg under the the Packages folder and they are automatically syndicated.