sln2003

Added by Elizaveta Revyakina, last edited by Christopher Hamilton on Feb 20, 2008  (view change)
Documentation Index

sln2003

This page contains reference information for the sln2003 Build Runner for Microsoft Visual Studio 2003 projects.

Note
  • The sln2003 build runner uses NAnt instead of MS Visual Studio 2003 to perform the build.  As a result the agent is required to have .NET Framework 1.1 installed, however under certain conditions .NET Framework SDK 1.1 might be required. This NAnt solution task may behave differently than MS Visual Studio 2003. See http://nant.sourceforge.net/release/latest/help/tasks/solution.html for details.
  • To use this runner you need to configure the NAnt runner.

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

The sln 2003 Runner Page in Version 3.0

Option Description
Build Runner
Select sln2003 from the drop-down list.
Solution File Path A path to the solution to be built is relative to the build working directory.
Example: 
vs-addin\addin\addin.sln
Configuration Specify the name of the solution configuration to build.
Artifact Paths Specify the artifacts as a comma-separated string.
Projects Output 
This group of options enables you to use the default output defined in the solution, or specify your own output path.
Override project output Check this option to override output path settings specified in the solution / project. The overriding path should be entered in the field Output directory for all projects.
If this option is not checked, all the build-related data will be uploaded to the bin/<solution configuration> directory.
Output directory for all projects This option is available, if Override project output option is checked. Specify the directory where the compiled targets will be placed.

Resolve URLs via Map Click this radio button, if you want to map the URL project path to the physical project path.  If this option is selected, specify mapping in the Type the URL's map field.

Type the URL's map
Click this link and specify the desired map in the text area. Use the following format: 
http://localhost:8111=myProjectPath/myProject
where
http://localhost:8111 is a host where the project will be uploaded and
myProjectPath/myProject is the project root
Resolve URLs via WebDAV Click this radio button, if you want the URLs to be resolved via WebDav.
Warning

Make sure that all the necessary files are properly updated. The build agent may not update information from VCS implicitly. 
MS Visual Studio Reference Path Check this option, if you want to automatically include reference path of MS Visual Studio to the build.
Run NUnit Tests for Specify .Net assemblies, where the NUnit tests to be run are stored. Multiple entries are comma-separated; usage of NAnt wildcards is enabled.
In the following example, TeamCity will search for the tests assemblies in all project directories and run these tests. 
**\*.dll
Note

All these wildcards are specified relative to the project directory.
Do not Run NUnit Tests for Specify .Net assemblies that should be excluded from the list of found assemblies to test. Multiple entries are comma-separated; usage of NAnt wildcards is enabled.
 In the following example, TeamCity will omit tests specified in this directory. 
**\obj\**\*.dll
Note

All these wildcards are specified relative to the project directory.
Build Working Directory Specify the Build Working Directory.

The sln 2003 Runner Page in Version 3.1

Option Description
Build Runner
Select sln2003 from the drop-down list.
Solution File Path A path to the solution to be built is relative to the Build Checkout Directory.
Example: 
vs-addin\addin\addin.sln
Working Directory Specify the Build Working Directory.
Configuration Specify the name of the solution configuration to build.
Projects Output
This group of options enables you to use the default output defined in the solution, or specify your own output path.
Output directory for all projects This option is available, if Override project output option is checked. Specify the directory where the compiled targets will be placed.

Resolve URLs via Map Click this radio button, if you want to map the URL project path to the physical project path.  If this option is selected, specify mapping in the Type the URL's map field.

Type the URL's map
Click this link and specify the desired map in the text area. Use the following format: 
http://localhost:8111=myProjectPath/myProject
where
http://localhost:8111 is a host where the project will be uploaded and
myProjectPath/myProject is the project root
Resolve URLs via WebDAV Click this radio button, if you want the URLs to be resolved via WebDav.
Warning

Make sure that all the necessary files are properly updated. The build agent may not update information from VCS implicitly. 
MS Visual Studio Reference Path Check this option, if you want to automatically include reference path of MS Visual Studio to the build.
Run NUnit Tests for Specify .Net assemblies, where the NUnit tests to be run are stored. Multiple entries are comma-separated; usage of NAnt wildcards is enabled.
In the following example, TeamCity will search for the tests assemblies in all project directories and run these tests. 
**\*.dll
Note

All these wildcards are specified relative to path that contains the solution file.
Do not Run NUnit Tests for Specify .Net assemblies that should be excluded from the list of found assemblies to test. Multiple entries are comma-separated; usage of NAnt wildcards is enabled.
 In the following example, TeamCity will omit tests specified in this directory. 
**\obj\**\*.dll
Note

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

See also:

Labels

 
(None)