This page contains reference information for the MSBuild Build Runner fields.
note
The MSBuild runner requires .Net Framework or Mono installed on the build agent. Since TeamCity 8.0.5 Microsoft Build Tools 2013 are also supported. Before setting up the build configuration to use MSBuild as the build runner, make sure you are using an XML build project file with the MSBuild runner. To build a Microsoft Visual Studio solution file, you can use the Visual Studio (sln) build runner.
General Build Runner Options
Option
Description
Build file path
Specify the path to the solution to be built relative to the Build Checkout Directory. For example:
Select the MSBuild version: .NET Framework or Mono xbuild. Since TeamCity 8.1, Microsoft Build Tools 2013 is also supported.
MSBuild ToolsVersion
Specify here the version of tools that will be used to compile (equivalent to the /toolsversion: commandline argument).
tip
MSBuild supports compilation to older versions, thus you may set MSBuild version as 4.0 with MSBuild ToolsVersion set to 2.0 to produce .NET 2.0 assemblies while running MSBuild from .NET Framework 4.0. For more information refer to http://msdn.microsoft.com/en-us/library/bb383796(VS.100).aspx
Run platform
From the drop-down list select the desired execution mode on a x64 machine.
Targets
A target is an arbitrary script for your project purposes. Enter targets separated by spaces.
Command line parameters
Specify any additional parameters for msbuild.exe
Reduce test failure feedback time
Use the following option to instruct TeamCity to run some tests before others.
MSBuild runner generates an MSBuild script that includes user's script. This script is used to add TeamCity provided msbuild tasks. Your MSBuild script will be included with the <Import> task. If you specified a Visual Studio solution file, it will be called from the <MSBuild> task. To disable it, set teamcity.msbuild.generateWrappingScript to false.