Label: msbuild

Content with label msbuild in TeamCity 4.x Documentation (See content from all spaces)
Related Labels: task , messages , property , draft , runner , nant , script , service , framework , nunit , addin , build , launcher , console , test

MSBuild
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 ...
MSBuild_
NET Testing Frameworks Support NUnit Support \\ See Also: Concepts: build runner Administrator Reference: NUnit for MSBuild
MSBuild Service Tasks
MSBuild, TeamCity provides the following service tasks that implement the same options as the service messages Build Script Interaction with TeamCity#Service Messages: TeamCitySetBuildNumber {{TeamCitySetBuildNumber}} allows user to change BuildNumber: <TeamCitySetBuildNumber BuildNumber="1.3 " /> It is possible to use '\ ' as a placeholder for older ...
NAnt_
Basic information on setting up the NAnt Build Runner can be found in the NAnt section of the UI Reference. This section contains information on working with the NAnt Runner. TeamCity supports NAnt 0.85 and NAnt 0.86 beta 1. Setting the NAntHome Environment ...
NUnit Addins Support
NUnit addin is an extension that plug into NUnit core and changes the way it operates. Refer to the NUnit addins page http://www.nunit.org/index.php?p=addins for more information. This section covers description of NUnit addins support for: NAnt build runner ...
NUnit for MSBuild
TeamCity provides custom {{NUnitTeamCity}} task and {{NUnit}} task that is compatible with {{NUnit}} task from MSBuild Community tasks http://msbuildtasks.tigris.org/ project. In order for these tasks to work the {{teamcitydotnetnunitlauncher}} system property have to be accessible. Build Agents running windows should ...
NUnit Support
run tests with NUnit, TeamCity: uses its own NUnit launcher TeamCity NUnit Test Launcher automatically replaces NUnit calls from NAnt runner NUnit for NAnt build runner with {{<nunit2>}} task automatically replaces NUnit calls ...