I Am Not Myself


Configuring and Using an Internal NuGet Server

My team has been moving to using NuGet to solve our dependency problem. Last week we put the final piece in place by publishing our internal shared libraries to an internal NuGet server.

This allows us to take advantage of the excellent .NET Open Source community, while keeping our “not for public” consumption libraries private. Our internal server hosts only our internal libraries and NuGet handles resolving all reference from the public package source. Which lends itself to a really clean workflow.

Next steps for us are to update to the latest version of TeamCity which has NuGet based build triggers.

Here is a quick video demonstrating how to use the internal/public feeds together from a users perspective in Visual Studio.

2 responses to “Configuring and Using an Internal NuGet Server

  1. av June 13, 2011 at 5:04 pm

    Awesome…thanks for the demo

  2. inka cola September 3, 2012 at 7:21 am

    Great I was wondering how to set up the nuget manager with our internal server without having to open one solution 🙂

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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

%d bloggers like this: