.NET CLI (dotnet)
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.
This page provides details on configuring the .NET CLI (dotnet) runner. Also see the related blog post.
.NET Core SDK has to be installed on your build agent machines.
The .NET CLI tools path has to be added to the
PATHenvironment variable. You can also configure the
DOTNET_HOMEenvironment variable for your TeamCity build agent user, for example,
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.
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.
Specify the target framework, for example, netcoreapp or netstandard. Parameter references are supported.
Specify the target configuration, for example, Release or Debug. Parameter references are supported.
Specify the target runtime. Parameter references are supported.
The directory where to place outputs. Parameter references are supported. If you have a finished build, you can use the file/directory selector here.
Defines the value of the
Command line parameters
Enter additional command line parameters for
Select from the <Default>, Minimal, Normal, Detailed or Diagnostic.
Since TeamCity 2018.1, the .NET CLI build step can be run in a specified Docker container.
JetBrains dotCover is supported as a coverage tool for the
Authentication in private NuGet Feeds
TeamCity allows you to authenticate using private NuGet feeds. Read more in NuGet.
Parameters Reported by Agent
When starting, the build agent reports the following parameters:
The .NET CLI version
The path to .NET CLI executable
The .NET Core SDK version