NuGet Installer build runner allows to pull NuGet packages required to build your project without having to commit them into the version control, which comes in handy especially when using a DVCS, like Mercurial or Git. Also it can (optionally) automatically update package dependencies to the most recent ones. Learn more about the problem and existing workarounds.
- Make sure that sources that you check out from VCS (VCS Settings) include the folder called
packages from your solution folder.
To configure NuGet Installer:
- Select NuGet version to use from the NuGet.exe drop-down list (if you have installed NuGet beforehand), or specify custom path to
- Specify NuGet package sources, for example your own NuGet repository. In case you're using TeamCity as NuGet repository, specify
%teamcity.nuget.feed.server% here. If you leave this field blank, NuGet will use nuget.org by default to search for your packages.
- Specify path to your solution file (.sln) where packages should be installed.
- If needed, select additional options:
- Exclude version from package folder names: Equivalent to
-ExcludeVersion NuGet commandline argument. If enabled, the destination folder will contain only the package name, not the version number.
- Update packages with help of NuGet update command: Uses NuGet update command to update all packages under solution. Package versions and constraints are taken from
- Perform safe update: Equivalent to
-Safe NuGet option, that looks for updates with the highest version available within the same major and minor version as the installed package.
Note, that for installing and updating packages we use
NuGet.exe install and
NuGet.exe update commands respectively. See NuGet documentation.
If you have added NuGet Installer to your build configuration, you will probably want to know the exact versions of packages used in builds. For this purpose, there's a NuGet Packages tab for every finished build that lists packages used.