dotnet-build - Man Page

• Compile the project or solution in the current directory: dotnet build
• Compile a .NET project or solution in debug mode: dotnet build path/to/project_or_solution
• Compile in release mode: dotnet build --configuration Release
• Compile without restoring dependencies: dotnet build --no-restore
• Compile with a specific verbosity level: dotnet build --verbosity quiet|minimal|normal|detailed|diagnostic
• Compile for a specific runtime: dotnet build --runtime runtime_identifier
• Specify the output directory: dotnet build --output path/to/directory

tldr.sh

This article applies to: ✓ .NET Core 1.x SDK and later versions

dotnet build [<PROJECT>|<SOLUTION>] [-c|--configuration] [-f|--framework] [--force]
    [--interactive] [--no-dependencies] [--no-incremental] [--no-restore] [--nologo] 
    [-o|--output] [-r|--runtime] [-v|--verbosity] [--version-suffix]

dotnet build [-h|--help]

The dotnet build command builds the project and its dependencies into a set of binaries. The binaries include the project’s code in Intermediate Language (IL) files with a .dll extension. Depending on the project type and settings, other files may be included, such as:

• An executable that can be used to run the application, if the project type is an executable targeting .NET Core 3.0 or later.
• Symbol files used for debugging with a .pdb extension.
• A .deps.json file, which lists the dependencies of the application or library.
• A .runtimeconfig.json file, which specifies the shared runtime and its version for an application.
• Other libraries that the project depends on (via project references or NuGet package references).

For executable projects targeting versions earlier than .NET Core 3.0, library dependencies from NuGet are typically NOT copied to the output folder. They’re resolved from the NuGet global packages folder at run time. With that in mind, the product of dotnet build isn’t ready to be transferred to another machine to run. To create a version of the application that can be deployed, you need to publish it (for example, with the dotnet publish command). For more information, see .NET Core Application Deployment.

For executable projects targeting .NET Core 3.0 and later, library dependencies are copied to the output folder. This means that if there isn’t any other publish-specific logic (such as Web projects have), the build output should be deployable.

Building requires the project.assets.json file, which lists the dependencies of your application. The file is created when dotnet restore is executed. Without the assets file in place, the tooling can’t resolve reference assemblies, which results in errors. With .NET Core 1.x SDK, you needed to explicitly run dotnet restore before running dotnet build. Starting with .NET Core 2.0 SDK, dotnet restore runs implicitly when you run dotnet build. If you want to disable implicit restore when running the build command, you can pass the --no-restore option.

Whether the project is executable or not is determined by the <OutputType> property in the project file. The following example shows a project that produces executable code:

<PropertyGroup>
  <OutputType>Exe</OutputType>
</PropertyGroup>

To produce a library, omit the <OutputType> property or change its value to Library. The IL DLL for a library doesn’t contain entry points and can’t be executed.

• -c|--configuration {Debug|Release}

  Defines the build configuration. The default for most projects is Debug, but you can override the build configuration settings in your project.

• -f|--framework <FRAMEWORK>

  Compiles for a specific framework. The framework must be defined in the project file.

• --force

  Forces all dependencies to be resolved even if the last restore was successful. Specifying this flag is the same as deleting the project.assets.json file. Available since .NET Core 2.0 SDK.

• -h|--help

  Prints out a short help for the command.

• --interactive

  Allows the command to stop and wait for user input or action. For example, to complete authentication. Available since .NET Core 3.0 SDK.

• --no-dependencies

  Ignores project-to-project (P2P) references and only builds the specified root project.

• --no-incremental

  Marks the build as unsafe for incremental build. This flag turns off incremental compilation and forces a clean rebuild of the project’s dependency graph.

• --no-restore

  Doesn’t execute an implicit restore during build. Available since .NET Core 2.0 SDK.

• --nologo

  Doesn’t display the startup banner or the copyright message. Available since .NET Core 3.0 SDK.

• -o|--output <OUTPUT_DIRECTORY>

  Directory in which to place the built binaries. If not specified, the default path is ./bin/<configuration>/<framework>/. For projects with multiple target frameworks (via the TargetFrameworks property), you also need to define --framework when you specify this option.

• -r|--runtime <RUNTIME_IDENTIFIER>

  Specifies the target runtime. For a list of Runtime Identifiers (RIDs), see the RID catalog.

• -v|--verbosity <LEVEL>

  Sets the MSBuild verbosity level. Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic]. The default is minimal.

• --version-suffix <VERSION_SUFFIX>

  Sets the value of the $(VersionSuffix) property to use when building the project. This only works if the $(Version) property isn’t set. Then, $(Version) is set to the $(VersionPrefix) combined with the $(VersionSuffix), separated by a dash.

• Build a project and its dependencies:

  dotnet build

• Build a project and its dependencies using Release configuration:

  dotnet build --configuration Release

• Build a project and its dependencies for a specific runtime (in this example, Ubuntu 18.04):

  dotnet build --runtime ubuntu.18.04-x64

• Build the project and use the specified NuGet package source during the restore operation (.NET Core 2.0 SDK and later versions):

  dotnet build --source c:\packages\mypackages

• Build the project and set version 1.2.3.4 as a build parameter using the -p MSBuild option:

  dotnet build -p:Version=1.2.3.4