NuGet for the Enterprise

NuGet is such a great tool that it’s surprising we have gone without it for so long. Most enterprise developers will make heavy use of it to leverage external libraries. Before long most enterprise companies will see a need to share their own libraries internally. They need a private NuGet server. Thanks to the excellent guys building NuGet, it’s free and low effort to setup your own server. Below is how I did it:

  1. Install Windows Server 2008 R2
  2. Install SQL Server 2012 Express
  3. Install IIS
  4. Install .Net 4
  5. run C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis -iru
  6. Checkout code from
  7. Run build.bat
  8. Copy \PackagedWebsite to \\yourserver\c$\inetpub\wwwroot


I did run into a few snags installing it. Here are a few more steps I performed after the above installation steps.

  1. I had to configure the IIS AppPool to run as a NETWORK_SERVICE. This allows access to SQL Server.
    1. Reference:
  2. Create & Grant IIS_Users access to a Lucene folder C:\inetpub\wwwroot\NuGet\App_Data\Lucene
  3. Create & Grant IIS_USERS access to the folder C:\inetpub\wwwroot\App_Data\Files\packages.


Here are the steps they give which are excellent to:

This entry was posted in .Net and tagged , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s