This means that if there isn't any other publish-specific logic (such as Web projects have), the build output should be deployable. NET Core 3.0 and later, library dependencies are copied to the output folder. NET Application Deployment.įor executable projects targeting. To create a version of the application that can be deployed, you need to publish it (for example, with the dotnet publish command). With that in mind, the product of dotnet build isn't ready to be transferred to another machine to run. They're resolved from the NuGet global packages folder at run time. NET Core 3.0, library dependencies from NuGet are typically NOT copied to the output folder.
An executable that can be used to run the application, if the project type is an executable targeting.
Depending on the project type and settings, other files may be included, such as: The binaries include the project's code in Intermediate Language (IL) files with a. The dotnet build command builds the project and its dependencies into a set of binaries. NET Core 3.1 SDK and later versions Nameĭotnet build - Builds a project and all of its dependencies.