This page contains reference information for the MSBuild Build Runner fields.
|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 2005, 2008 or 2010 solution file please use the Visual Studio (sln) build runner).|
General Build Runner Options
| Build File Path
|| Specify the path to the solution to be built, relative to the Build Checkout Directory. For example:
|Alternatively, click to choose the file using VCS repository browser (Currently VCS repository browser is only available for Git, Mercurial, Subversion and Perforce. )|
| Working Directory
|| Specify the path to the build working directory.
| MSBuild version
|| Select the framework you want to run - either .NET Framework (2.0, 3.5 or 4.0) or Mono xbuild.
|| Specify here the version of tools that will be used to compile (equivalent to /toolsversion: commandline argument).
| Run platform
|| From the drop-down list select the desired execution mode on a x64 machine.
|| Enter targets separated by spaces. A target is an arbitrary script for your project purposes.
| 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.
To learn about configuring code coverage options, please refer to the Configuring .NET Code Coverage page.
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 <Import> task. If you specified a Visual Studio solution file, it will be called from <MSBuild> task. To disable it, set teamcity.msbuild.generateWrappingScript configuration parameter with value false.