Team Services | TFS 2017 | TFS 2015 | Previous versions (XAML builds)
Install and update NuGet package dependencies.
Looking for help to get started? See Use Team Build to restore and publish NuGet packages.
If your code depends on NuGet packages, make sure to add this step before your Visual Studio Build step. Also make sure to clear the deprecated Restore NuGetPackages checkbox in that step.
|Path to Solution||
Copy the value from the Solution argument in your Visual Studio Build step and paste it here.
|Path to NuGet.config||
If you are using a package source other than NuGet.org, you must check in a NuGet.config file and specify the path to it here.
|Disable local cache||
Equivalent to nuget restore with the
|NuGet Arguments||Additional arguments passed to nuget restore.|
|Path to NuGet.exe||(Optional) Path to your own instance of NuGet.exe. If you specify this argument, you must have your own strategy to handle authentication.|
Install NuGet dependencies
You're building a Visual Studio solution that depends on a NuGet feed.
`-- ConsoleApplication1 |-- ConsoleApplication1.sln |-- NuGet.config `-- ConsoleApplication1 |-- ConsoleApplication1.csproj
Package: NuGet Installer
Install your NuGet package dependencies.
Build: Visual Studio Build
Build your solution.
NuGet Packager Create a NuGet package from either a .csproj or .nuspec file
NuGet Publisher Publish your NuGet package to a server and update your feed
Q & A
Where can I learn about Visual Studio Team Services package management?
Where can I learn more about NuGet?
NuGet Docs Overview
NuGet Create Packaging and publishing
NuGet Consume Seting up a solution to get dependencies
What other kinds of apps can I build?
What other kinds of build steps are available?
How do we protect our codebase from build breaks?
Git: Improve code quality with branch policies with an option to require that code builds before it can be merged to a branch. This option is not available for GitHub repos.
TFVC: Use gated check-in.
How do I modify other parts of my build definition?
Specify your build steps to run tests, scripts, and a wide range of other processes.
Specify build options such as specifying how completed builds are named, building multiple configurations, creating work items on failure.
Specify the repository to pick the source of the build and modify options such as how the agent workspace is cleaned.
Set build triggers to modify how your CI builds run and to specify scheduled builds.
Specify build retention policies to automatically delete old builds.
I selected parallel multi-configuration, but only one build is running at a time.
If you're using Team Services, you might need more concurrent pipelines. See Concurrent build and release pipelines in Visual Studio Team Services.
How do I see what has changed in my build definition?
Do I need a build agent?
You need at least one agent to run your build. Get an agent.
I can't select a default agent queue and I can't queue my build. How do I fix this?