.NET CLI (dotnet)
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.
Option | Description |
---|---|
Command: | Select a |
Projects: | 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 |
Command line parameters: | Enter additional command line parameters for |
Logging verbosity: | Select from the <Default>, Minimal, Normal, Detailed or Diagnostic. |
Code Coverage
JetBrains dotCover is supported as a coverage tool for the msbuild
, test
, and vstest
commands.
Parameters Reported by Agent
When starting, the build agent reports the following parameters:
Parameter | Description |
---|---|
| The .NET CLI version |
| The path to .NET CLI executable |
| The .NET Core SDK version |