Starting from TeamCity 2017.2, TeamCity comes with built-in support of .NET CLI toolchain providing .NET CLI (dotnet) build steps, CLI detection on the build agents, and auto-discovery of build steps in your repository. If you manually installed the .NET CLI (.NET Core) plugin for the previous version, please remove it.
This page provides details on configuring the .NET CLI (dotnet) runner. Also see the related blog post.
note
.NET Core SDK has to be installed on your build agent machines.
The .NET CLI tools path has to be added to the PATH environment variable. You can also configure the DOTNET_HOME environment variable for your TeamCity build agent user, e.g: DOTNET_HOME=C:\Program Files\dotnet\
Option
Description
Command:
Select a dotnet command from the drop-down. Depending on the selected command, some of the options below will vary. The currently supported commands are:
Specify paths to projects and solutions. Wildcards are supported. Parameter references are supported. If you have a finished build, you can use the file/directory chooser here.
Working directory:
Optional, set if differs from the checkout directory. Parameter references are supported. If you have a finished build, you can use the file/directory chooser here.
Framework:
Specify the target framework, e.g. netcoreapp or netstandard. Parameter references are supported.
Configuration:
Specify the target configuration, e.g. Release or Debug. Parameter references are supported.
Runtime:
Specify the target runtime. Parameter references are supported.
Output directory:
The directory where to place outputs.arameter references are supported. If you have a finished build, you can use the file/directory chooser here.
Version suffix:
Defines the value of the$(VersionSuffix) property in the project. Parameter references are supported.