Internal (private) NuGet servers

By | July 19, 2013

I just posted this to my blog at work but thought I’d also pass it along to my .Netitude readers. Hope you find it useful!

If you’re familiar with NuGet you know the benefits it provides .Net developers in consuming packages created by 3rd parties. Well, what if you want to treat somebody internal to your organization as a 3rd party, and don’t want the whole outside world to see the packages you put together for them?

You have a couple of options:

  1. Sign up for a service like which will host a private NuGet feed for you to which you can upload packages and control access (even at an Enterprise level if you want to pay for it)
  2. Create your own “server” using the instructions below

Obviously I’m going to outline #2.

I put server in quotes because it’s insanely easy to do this and isn’t even really a server.

I have set up my own NuGet server internally, you can use it in VS by setting up the following:


Notice the ‘source’ – it’s just a network share.

When you set this up you’ll get the following in your “Manage NuGet packages…” dialog:



You can hit ‘Install’ and get a .cs file that has an extension class in it. Useless as it may be to you at this point. :)