Since version 2020.2, the Visual Studio 2003 build runner is discontinued and disabled in TeamCity.
We recommend switching to the .NET build runner instead. If you were actively using the VS 2003 runner and cannot easily migrate to the .NET runner, please let us know about it via any of our feedback channels.
The Visual Studio 2003 build runner supports building Microsoft Visual Studio 2003 .NET projects. To build Microsoft Visual Studio 2005-2017 projects, see Visual Studio (sln) Build Runner.
note
The Visual Studio 2003 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 NAnt documentation for details. To use this runner you need to configure the NAnt runner.
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:
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.
NAnt home
Specify path to the NAnt executable to run builds of the build configuration. The path can be absolute, relative to the build checkout directory; also you can use an environment variable.
Command line parameters
Specify any additional parameters for NAnt.exe.
TeamCity passes automatically to NAnt all defined system properties, so you do not need to specify all of the properties here via -D option. You can create necessary properties at the Build Parameters section of the Build Configuration Settings.
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
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
All these wildcards are specified relative to path that contains the solution file.
Reduce test failure feedback time
Use 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)