TeamCity
 
3.0
You are viewing the documentation for an earlier version of TeamCity.
  1. TeamCity Documentation
  2. UI Reference
  3. Administration
  4. Create Edit Build Configuration
  5. 3.Build Runners
  6. Visual Studio 2005

Visual Studio 2005

Last modified: 20 April 2023

This page contains reference information for sln2005 Build Runner that builds Microsoft Visual Studio 2005 solution files. Note that sln2005 works the same as sln2008 only it uses MSBuild from .NET version 2.0.

note

Please note that the page was restructured between versions 3.0 and 3.1. Please refer to the applicable description: ver30 or ver31.

The sln 2005 Runner Page in Version 3.0



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 working directory. Example:

vs-addin\addin\addin.sln

Artifact Paths

Specify Build Artifact as a comma-separated string.

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.

Run NUnit/VSTS Unit tests for

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.

**\*.dll

tip

All these wildcards are specified relative to the project directory.

Do not run NUnit/VSTS Unit tests for

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.

**\obj\**\*.dll

tip

All these wildcards are specified relative to the project directory.

Build Working Directory

Specify the build working directory.

The sln 2005 Runner Page in Version 3.1



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. Example:

vs-addin\addin\addin.sln

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.

Run NUnit/VSTS Unit tests for

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.

**\*.dll

tip

All these wildcards are specified relative to path that contains the solution file.

Do not run NUnit/VSTS Unit tests for

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.

**\obj\**\*.dll

tip

All these wildcards are specified relative to path that contains the solution file.