TeamCity integrates with NuGet package manager and allows you to:
You don't need to manually install the required NuGet.exe Command Line tool to all build agents, TeamCity can do this automatically. You need only to choose which NuGet versions you want to be installed on agents at Administration | NuGet Settings | NuGet Commandline tab. Starting with TeamCity 7.1 you can also upload your own NuGet.CommandLine package instead of downloading it from the public feed.
If for some reason you don't want to publish packages to public feed, e.g. you're producing packages that are intended to be used internally; you can use TeamCity as native NuGet Server instead of setting up your own repository. To start using TeamCity as NuGet Server you need to enable TeamCity server to be a NuGet server by clicking corresponding button at Administration | NuGet Settings | NuGet Server page. Two different links will be displayed on the same page: for public (with guestAuth prefix) and private (with httpAuth prefix) feed. If Public Url is not available, you need to enable the Guest user login in TeamCity at Administration | Global Settings page.
For an example of set up see blog post: Setting up TeamCity as a native NuGet Server
When you have TeamCity NuGet server enabled:
Skip to end of metadata Go to start of metadata