Hosting Your Own NuGet Feeds

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 intranet or internet URL).

There are several third-party NuGet Servers available that make remote private feeds easy to configure and set-up, including Visual Studio Team Services, MyGet, Inedo's ProGet, JFrog's Artifactory, NuGet Server, and Sonatype's Nexus. See An Overview of the NuGet Ecosystem to learn more about these options.

Local feeds come in two flavors: a folder of nupkg files and a versioned set of hierarchical folders. Starting with NuGet 3.3, you can create and install packages much faster with the hierarchical folder structure.

You can create a local feed on disk or build your own remote feed using NuGet's server components by following the instructions below.

Creating Local Feeds

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.

Package Manager Settings in menu

The Package Sources under Package Manager node in Options dialog box is displayed.

Options dialog box

In the Name box, enter a name for your feed. In the Source box enter the path of your packages folder.

Available Package Sources dialog box without new feed

Click Update. 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.

Selecting local feed in Package Manager Console

You can also select the new feed in the Online tab of the Manage NuGet Packages dialog box.

Selecting local feed in the Manage NuGet Packages dialog

Creating Local Feeds v3.3+

Starting with NuGet 3.3, you can create and manage a folder of packages that can be referenced by the NuGet clients in the same way as described in the previous section. To manage this folder, you will need a copy of the NuGet command-line tool.

Start by creating an empty folder that will contain the new hierarchical NuGet feed. Let's refer to that folder as $folder. If you have an existing folder of packages at $existing that you would like to add to $folder, execute the following command:

nuget init $existing $folder

As new and updated packages like package.nupkg are created that you would like to add to the folder, execute the following command:

nuget add package.nupkg -source $folder

Finally, add a reference to $folder in your NuGet configuration as specified above.

Creating Remote Feeds

You can also host a remote (or internal) feed on a server that runs IIS. There are two alternatives from the NuGet team here

  1. NuGet.Server
  2. NuGet Gallery

NuGet.Server is ideal when a simple NuGet server is desired. It is basically a view of a network share or local folder through http(s), and as such is easy to setup. The NuGet Gallery Project provides user management and additional features such as an extensive web UI that allows searching and exploring packages from within the browser, similar to

Other alternatives are available as well - check the Overview of the NuGet Ecosystem to learn more about these.

Below are the instruction to host a NuGet.Server, the instructions for setting up NuGet Gallery are in the link above.

Step 1: Create a new Empty Web Application in Visual Studio

Go to the File | New | Project menu option (or just hit CTRL + SHIFT + N) which will bring up the new project dialog. Select ASP.NET Web Application as in the following screenshot. Please note that the steps here including NuGet.Server package are intended for use with C# project only.

New Project dialog box

Next, select the ASP.NET 4.6 - Empty template (or higher .NET version) and create the project. This results in a very empty project.

New project in Solution Explorer

Step 2: Install the NuGet.Server Package

Now right click on the project node and select Manage NuGet Packages to launch the NuGet dialog (alternatively, you can use the Package Manager Console instead and type Install-Package NuGet.Server).

Click the Browse 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 package

Step 3: Configure the Packages folder

Starting with NuGet.Server 1.5, you can configure the folder which contains your packages. The web.config file contains a new appSetting, named 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.

    <!-- Set the value here to specify your custom packages folder. -->
    <add key="packagesPath" value="C:\MyPackages" />

Step 4: Add Packages to the Packages folder

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 a few packages that have been added manually to the default Packages folder.

Adding packages to the 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 include the .nupkg files in Solution Explorer and change the Build Action property to "Content".

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 `appSetting`, named `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. 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. ### Step 5: Deploy and run your brand new Package Feed! Hit CTRL + F5 to run the site and it'll provide some instructions on what to do next. ![Package feed home page](/images/create/Package-feed-home-page.png) Clicking on "here" shows the OData over ATOM feed of packages. ![OData over ATOM package feed](/images/create/OData-over-ATOM-package-feed.png)

After the first load of the feed, the Packages folder is restructured:

NuGet.Server uses the local storage layout introduced with NuGet 3.3 to store packages and will always copy packages that are added to the Packages folder manually to a subfolder that follows this new storage layout. More information about performance improvements added in the latest NuGet.Server package can be found on our blog.

Now all we need to do is deploy this website as we would any other site and then we can click NuGet's Settings button and add this feed to my set of package sources.

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.