This article applies to: ✓ .NET Core 1.x SDK and later versions
dotnet build - Builds a project and all of its dependencies.
dotnet build [<PROJECT>|<SOLUTION>] [-c|--configuration] [-f|--framework] [--force] [--interactive] [--no-dependencies] [--no-incremental] [--nologo] [--no-restore] [-o|--output] [-r|--runtime] [-v|--verbosity] [--version-suffix] dotnet build [-h|--help]
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 and symbol files used for debugging with a .pdb extension. A dependencies JSON file (.deps.json) is produced that lists the dependencies of the application. A .runtimeconfig.json file is produced, which specifies the shared runtime and its version for the application.
If the project has third-party dependencies, such as libraries from NuGet, they're resolved from the NuGet cache and aren't available with the project's built output. With that in mind, the product of
dotnet build isn't ready to be transferred to another machine to run. This is in contrast to the behavior of the .NET Framework in which building an executable project (an application) produces output that's runnable on any machine where the .NET Framework is installed. To have a similar experience with .NET Core, you need to use the dotnet publish command. For more information, see .NET Core Application Deployment.
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 the
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
Starting with .NET Core 2.0, you don't have to run
dotnet restore because it's run implicitly by all commands, such as
dotnet build and
dotnet run, that require a restore to occur. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as continuous integration builds in Azure DevOps Services or in build systems that need to explicitly control the time at which the restore occurs.
This command also supports the
dotnet restore options when passed in the long form (for example,
--source). Short form options, such as
-s, are not supported.
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. The main difference in built output is that the IL DLL for a library doesn't contain entry points and can't be executed.
dotnet build uses MSBuild to build the project, so it supports both parallel and incremental builds. For more information, see Incremental Builds.
In addition to its options, the
dotnet build command accepts MSBuild options, such as
-p for setting properties or
-l to define a logger. For more information about these options, see the MSBuild Command-Line Reference. Or you can also use the dotnet msbuild command.
dotnet build is equivalent to
dotnet msbuild -restore -target:Build.
PROJECT | SOLUTION
The project or solution file to build. If a project or solution file isn't specified, MSBuild searches the current working directory for a file that has a file extension that ends in either proj or sln and uses that file.
Defines the build configuration. The default value is
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.
Prints out a short help for the command.
Allows the command to stop and wait for user input or action. For example, to complete authentication. Available since .NET Core 3.0 SDK.
Ignores project-to-project (P2P) references and only builds the specified root project.
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.
Doesn't display the startup banner or the copyright message. Available since .NET Core 3.0 SDK.
Doesn't execute an implicit restore during build. Available since .NET Core 2.0 SDK.
Directory in which to place the built binaries. You also need to define
--frameworkwhen you specify this option. If not specified, the default path is
Specifies the target runtime. For a list of Runtime Identifiers (RIDs), see the RID catalog.
Sets the MSBuild verbosity level. Allowed values are
diag[nostic]. The default is
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:
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 220.127.116.11 as a build parameter using the
dotnet build -p:Version=18.104.22.168