Add dotnet-tool manpages and update others

This commit is contained in:
kasper3 2018-05-30 15:50:26 +00:00
parent de407deff0
commit 5f93685491
29 changed files with 1895 additions and 215 deletions

View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet build command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -44,19 +44,19 @@ For more information, see .NET Core Application Deployment.
Building requires the \f[I]project.assets.json\f[] file, which lists the dependencies of your application.
The file is created when \f[C]dotnet\ restore\f[] is executed.
Without the assets file in place, the tooling cannot resolve reference assemblies, which results in errors.
With .NET Core 1.x SDK, you needed to explicitily run the \f[C]dotnet\ restore\f[] before running \f[C]dotnet\ build\f[].
Starting with .NET Core 2.0 SDK, \f[C]dotnet\ restore\f[] runs implicitily when you run \f[C]dotnet\ build\f[].
With .NET Core 1.x SDK, you needed to explicitly run the \f[C]dotnet\ restore\f[] before running \f[C]dotnet\ build\f[].
Starting with .NET Core 2.0 SDK, \f[C]dotnet\ restore\f[] runs implicitly when you run \f[C]dotnet\ build\f[].
If you want to disable implicit restore when running the build command, you can pass the \f[C]\-\-no\-restore\f[] option.
.PP
.PP
\f[C]dotnet\ build\f[] uses MSBuild to build the project; thus, it supports both parallel and incremental builds.
Refer to Incremental Builds for more information.
\f[C]dotnet\ build\f[] uses MSBuild to build the project, so it supports both parallel and incremental builds.
For more information, see Incremental Builds.
.PP
In addition to its options, the \f[C]dotnet\ build\f[] command accepts MSBuild options, such as \f[C]/p\f[] for setting properties or \f[C]/l\f[] to define a logger.
Learn more about these options in the MSBuild Command\-Line Reference.
For more information about these options, see the MSBuild Command\-Line Reference.
.PP
Whether the project is executable or not is determined by the \f[C]<OutputType>\f[] property in the project file.
The following example shows a project that will produce executable code:
The following example shows a project that produces executable code:
.IP
.nf
\f[C]
@ -90,7 +90,7 @@ The framework must be defined in the project file.
\f[C]\-\-force\f[]
.PP
Forces all dependencies to be resolved even if the last restore was successful.
This is equivalent to deleting the \f[I]project.assets.json\f[] file.
Specifying this flag is the same as deleting the \f[I]project.assets.json\f[] file.
.PP
\f[C]\-h|\-\-help\f[]
.PP
@ -98,16 +98,16 @@ Prints out a short help for the command.
.PP
\f[C]\-\-no\-dependencies\f[]
.PP
Ignores project\-to\-project (P2P) references and only builds the root project specified to build.
Ignores project\-to\-project (P2P) references and only builds the specified root project.
.PP
\f[C]\-\-no\-incremental\f[]
.PP
Marks the build as unsafe for incremental build.
This turns off incremental compilation and forces a clean rebuild of the project's dependency graph.
This flag turns off incremental compilation and forces a clean rebuild of the project's dependency graph.
.PP
\f[C]\-\-no\-restore\f[]
.PP
Doesn't perform an implicit restore during build.
Doesn't execute an implicit restore during build.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
@ -146,12 +146,12 @@ Prints out a short help for the command.
.PP
\f[C]\-\-no\-dependencies\f[]
.PP
Ignores project\-to\-project (P2P) references and only builds the root project specified to build.
Ignores project\-to\-project (P2P) references and only builds the specified root project.
.PP
\f[C]\-\-no\-incremental\f[]
.PP
Marks the build as unsafe for incremental build.
This turns off incremental compilation and forces a clean rebuild of the project's dependency graph.
This flag turns off incremental compilation and forces a clean rebuild of the project's dependency graph.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP