sln2005

Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 4.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
Search

Searching TeamCity 4.x Documentation

Table of Contents

This page contains reference information for sln2005 Build Runner that builds Microsoft Visual Studio 2005 solution files.

sln2005 works the same as sln2008 only it uses MSBuild from .NET version 2.0.

General settings

Option Description
Build runner
Select sln2005 from the drop-down list.
Solution file path Specify the path to the solution to be built relative to the Build Checkout Directory. For example:
Working directory Specify the Build Working Directory.
Targets Specify the Microsoft Visual Studio 2005-specific targets. The possible options are Build, Rebuild, Clean, Publish or a combination of these targets based on your needs. Multiple targets are space-separated.
Configuration Specify the name of the MS VS 2005 solution configuration to build.
Platform

Specify the platform for the solution. You can leave this field blank, and TeamCity obtains this information from the solution settings.
NUnit tests settings Use this section to specify NUnit parameters
Tests platform From the drop-down list select the desired execution mode on a x64 machine. Supported values are: x86, x64 and Auto (MSIL)

NUnit test runner settings

NUnit tests settings Use this section to specify NUnit parameters
Tests platform From the drop-down list select the desired execution mode on a x64 machine. Supported values are: Auto (MSIL) (default), x86 and x64.
NUnit runner From the drop-down list select a version of the NUnit runner to use.
NUnit versions support
TeamCity NUnit Test Launcher supports NUnit versions 2.2.10, 2.4.1, 2.4.6, 2.4.7, 2.4.8, and 2.5.0.
TeamCity Addin for NUnit supports only 2.4.6, 2.4.7, 2.4.8, and 2.5.0.
TeamCity 4.5.6+ supports NUnit 2.5.2, and 2.5.3.
Run tests from Specify the .Net assemblies, where the NUnit tests to be run are stored. Multiple entries are comma-separated; usage of MSBuild wildcards is enabled.
In the following example, TeamCity will search for the tests assemblies in all project directories and run these tests.
All these wildcards are specified relative to path that contains the solution file.
Do not run tests from Specify .Net assemblies that should excluded from the list of found assemblies to test. Multiple entries are comma-separated; usage of MSBuild wildcards is enabled.
In the following example, TeamCity will omit tests specified in this directory.
All these wildcards are specified relative to path that contains the solution file.
NUnit categories include Specify NUnit categories of tests that should be run. Multiple entries are comma-separated.
NUnit categories exclude Specify NUnit categories that should be excluded from the tests to be run. Multiple entries are comma-separated.
Reduce test failure feedback time Use the following option to instruct TeamCity to run some tests before others.
Run recently failed tests first If checked, in the first place TeamCity will run tests failed in previous finished or running builds as well as tests having high failure rate (a so called blinking tests)




See Also:

Labels:

build build Delete
runner runner Delete
sln2005 sln2005 Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.