The DotNet Build action in Continua CI is a wrapper around the .Net Core command line tools. If you're having trouble using the DotNet Build action, please refer to the .NET Core Command Line Tools documentation. |
The DotNet action is used to build .Net Core projects
A friendly name for this action (will be displayed in the actions workflow area).
Determines if this action will be run within the relevant stage.
One or more paths to the project files to compile. These can be one or multiple paths to file, project directory or globbing pattern that matches project.json files. Note that relative paths are rooted in the workspace folder and globbing patterns are pased directly to the dotNet command line.
The working folder while running the command line. This defaults to the workspace folder.
The path to the folder in which to place the build binaries. Relative paths will be anchored to the workspace folder.
The path to the folder in which to temporary build files. By default, they go to the obj directory under the project directory. Relative paths will be anchored to the workspace folder.
The Using drop down is populated with any property collector whose namespace matches the pattern defined by the DotNet CLI Actions. The pattern for this action is ^DotNet.Cli.*
If you create a property collector for this action, make sure you select the Path Finder PlugIn type and give it a name that will match the pattern above in blue.
For more in-depth explanations on property collectors see Managing Property Collectors.
Alternatively, you can select the Custom option from the Using drop down list and specify a path in the resulting input field that will be displayed. Please read Why it's a good idea to use a property collector before using this option.
The name of the framework to compile for. The framework must also be defined in the project.json file.
The configuration under which to build. This defaults to "Debug" if left empty.
Target runtime identifier to build for.
Defines what * should be replaced with in the version field in the project.json file. The format follows NuGet's version guidelines.
Multiple environment variables can be defined - one per line. These are set before the Grunt command line is run.