.NET Process Runner

Edit pageLast modified: 12 March 2025

note

Since TeamCity 2020.1.1, we have stopped providing active support for the .NET Process runner.

To run any .NET process in your build, it is recommended to use the .NET runner with the \<custom\> command instead. This runner is actively supported and provides more benefits comparing to the .NET Process runner (such as code coverage and ability to run a process inside a Docker/Podman container).

The .NET Process Runner is able to run any .NET assembly under the selected .NET Framework version and platform, optionally with .NET code coverage. You can use it to run xUnit, Gallio or other .NET tests, for which there is no dedicated build runner.

note

The runner requires .NET Framework installed on the TeamCity Agent.

.NET Process Runner Settings

Option

Description

Path

Specify the path to a .NET executable (for example, to the xUnit console)

Command line parameters

Provide newline\- or space\-separated command line parameters to be passed to the executable.

Working directory

Specify the Build Working Directory if it differs from the Build Checkout Directory.

.NET Runtime

From the Platform drop\-down select the desired execution mode on a x64 machine. The supported values are: Auto (MSIL) (default), x86 and x64.
From the Version drop\-down select the desired .NET Framework version.

tip

If you have an MSIL .NET 2.0/3.5 executable, TeamCity can enforce it to execute under any required runtime: x86 or x64, and .NET 2.0 or .NET 4.0 runtime.

Code Coverage

If needed, add code coverage.

Note that you do not need to write any additional build scripts.

See also

Administrator's Guide