mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'release/2.1.4xx' into merges/release/2.1.3xx-to-release/2.1.4xx

Browse source
This commit is contained in:
John Beisner 2018-07-16 08:17:58 -07:00 • committed by GitHub
commit 85d732a5a1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
538 changed files with 10015 additions and 6166 deletions
Download patch file Download diff file Expand all files Collapse all files

16
Documentation/manpages/sdk/dotnet-add-package.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet add package command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -9,7 +9,7 @@
\f[C]dotnet\ add\ package\f[] \- Adds a package reference to a project file.
.SH SYNOPSIS
.PP
\f[C]dotnet\ add\ [<PROJECT>]\ package\ <PACKAGE_NAME>\ [\-h|\-\-help]\ [\-v|\-\-version]\ [\-f|\-\-framework]\ [\-n|\-\-no\-restore]\ [\-s|\-\-source]\ [\-\-package\-directory]\f[]
\f[C]dotnet\ add\ [<PROJECT>]\ package\ <PACKAGE_NAME>\ [\-h|\-\-help]\ [\-f|\-\-framework]\ [\-n|\-\-no\-restore]\ [\-\-package\-directory]\ [\-s|\-\-source]\ [\-v|\-\-version]\f[]
.SH DESCRIPTION
.PP
The \f[C]dotnet\ add\ package\f[] command provides a convenient option to add a package reference to a project file.
@ -54,10 +54,6 @@ The package reference to add.
.PP
Prints out a short help for the command.
.PP
\f[C]\-v|\-\-version\ <VERSION>\f[]
.PP
Version of the package.
.PP
\f[C]\-f|\-\-framework\ <FRAMEWORK>\f[]
.PP
Adds a package reference only when targeting a specific framework.
@ -66,13 +62,17 @@ Adds a package reference only when targeting a specific framework.
.PP
Adds a package reference without performing a restore preview and compatibility check.
.PP
\f[C]\-\-package\-directory\ <PACKAGE_DIRECTORY>\f[]
.PP
Restores the package to the specified directory.
.PP
\f[C]\-s|\-\-source\ <SOURCE>\f[]
.PP
Uses a specific NuGet package source during the restore operation.
.PP
\f[C]\-\-package\-directory\ <PACKAGE_DIRECTORY>\f[]
\f[C]\-v|\-\-version\ <VERSION>\f[]
.PP
Restores the package to the specified directory.
Version of the package.
.SH EXAMPLES
.PP
Add \f[C]Newtonsoft.Json\f[] NuGet package to a project:

2
Documentation/manpages/sdk/dotnet-add-reference.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet\-add reference command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy

43
Documentation/manpages/sdk/dotnet-build-server.1 Normal file
View file

@ -0,0 +1,43 @@
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet build\-server command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
.SH dotnet\-build
.PP
.SH NAME
.PP
\f[C]dotnet\ build\-server\f[] \- Interacts with servers started by a build.
.SH SYNOPSIS
.IP
.nf
\f[C]
dotnet\ build\-server\ shutdown\ [\-\-msbuild]\ [\-\-razor]\ [\-\-vbcscompiler]
dotnet\ build\-server\ shutdown\ [\-h|\-\-help]
dotnet\ build\-server\ [\-h|\-\-help]
\f[]
.fi
.SS Commands
.PP
\f[C]shutdown\f[]
.PP
Shuts down build servers that are started from dotnet.
By default, all servers are shut down.
.SH OPTIONS
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-\-msbuild\f[]
.PP
Shuts down the MSBuild build server.
.PP
\f[C]\-\-razor\f[]
.PP
Shuts down the Razor build server.
.PP
\f[C]\-\-vbcscompiler\f[]
.PP
Shuts down the VB/C# compiler build server.
.SH AUTHORS
mairaw.

26
Documentation/manpages/sdk/dotnet-build.1
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

2
Documentation/manpages/sdk/dotnet-clean.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet clean command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy

125
Documentation/manpages/sdk/dotnet-compile-native.1
View file

@ -1,125 +0,0 @@
.\" Automatically generated by Pandoc 1.15.1
.\"
.hy
.TH "dotnet-native" "1" "January 2016" "" ""
.SH NAME
.PP
dotnet\-compile\-native \-\- Compiles IL binaries to native binaries.
.SH SYNOPSIS
.PP
dotnet compile [\-\-appdepsdk] [\-\-configuration] [\-\-ilcargs]
[\-\-linklib] [\-\-logpath] [\-\-mode] [\-\-out] [\-\-reference]
[\-\-temp\-out] [\-\-verbose]
.SH DESCRIPTION
.PP
The \f[C]compile\-native\f[] command compiles IL assemblies to native
machine code.
It is used by \f[C]dotnet\-compile\ \-\-native\f[].
.PP
The output is a native exe that conforms to the architecture of the
underlying operating system (i.e.
running on 64\-bit OS will produce a native 64\-bit exe).
This can be overriden via the \-\-arch switch and specifying the wanted
architecture.
The executable has a default extension of "" on Linux and OS X and
".exe" on Windows.
The source must include a `static void Main(string[] args) entry point
and specify compilationOptions.emitEntryPoint in the project.json.
.PP
Output files are written to the child \f[C]bin\f[] folder, which will be
created if it doesn\[aq]t exist.
Files will be overwritten as needed.
.SH OPTIONS
.PP
\f[C]\-\-appdepsdk\ <SDK_PATH>\f[]
.IP
.nf
\f[C]
Path\ to\ custom\ AppDepSDK
\f[]
.fi
.PP
\f[C]\-c,\ \-\-configuration\ [debug|release]\f[]
.IP
.nf
\f[C]
Build\ configuration.\ Defaults\ to\ `debug`.
\f[]
.fi
.PP
\f[C]\-\-ilcargs\ <args>\f[]
.IP
.nf
\f[C]
Custom\ arguments\ for\ the\ IL\ Compiler.
\f[]
.fi
.PP
\f[C]\-\-ilcpath\ <ILC_PATH>\f[]
.IP
.nf
\f[C]
Path\ to\ a\ custom\ ilc.exe
\f[]
.fi
.PP
\f[C]\-\-linklib\ <LIB_PATH>\f[]
.IP
.nf
\f[C]
Path\ to\ static\ lib\ to\ link
\f[]
.fi
.PP
\f[C]\-\-logpath\ <LOG_PATH>\f[]
.IP
.nf
\f[C]
Enables\ logging\ and\ writes\ native\ compilation\ logs\ to\ the\ given\ path.
\f[]
.fi
.PP
\f[C]\-m,\ \-\-mode\ [cpp|ryujit|custom]\f[]
.IP
.nf
\f[C]
Code\ generation\ mode.\ Defaults\ to\ ryujit.
\f[]
.fi
.PP
\f[C]\-o,\ \-\-out\ directoryname\f[]
.IP
.nf
\f[C]
Output\ directory\ for\ the\ native\ executable.
\f[]
.fi
.PP
\f[C]\-r,\ \-\-reference\f[]
.IP
.nf
\f[C]
Path\ to\ a\ managed\ dll\ reference\ for\ the\ app.
\f[]
.fi
.PP
\f[C]\-t,\ \-\-temp\-out\f[]
.IP
.nf
\f[C]
Specifies\ temporary\ directory\ for\ intermediate\ files.
\f[]
.fi
.PP
\f[C]\-v,\ \-\-verbose\f[]
.IP
.nf
\f[C]
Prints\ verbose\ logging\ information,\ to\ follow\ the\ flow\ of\ execution\ of\ the\ command.
\f[]
.fi
.SH SEE ALSO
.PP
dotnet\-compile(1), dotnet(1), dotnet\-restore(1)
.SH AUTHORS
Zlatko Knezevic zlakne\@microsoft.com.

157
Documentation/manpages/sdk/dotnet-compile.1
View file

@ -1,157 +0,0 @@
.\" Automatically generated by Pandoc 1.15.1
.\"
.hy
.TH "dotnet-compiler" "1" "January 2016" "" ""
.SH NAME
.PP
dotnet\-compile \-\- Compiles source files for a single project to a
binary format and saves to a target file.
.SH SYNOPSIS
.PP
dotnet compile [\-\-native] [\-\-output] [\-\-temp\-output]
[\-\-framework] [\-\-configuration] [\-\-output] [\-\-arch] [\-\-cpp]
[\-ilc\-args] [\-\-verbose]
.SH DESCRIPTION
.PP
The compile command compiles source files from a single project to a
binary file, either intermediate language (IL) byte code or native
machine code, depending on the options provided.
The default option is compilation to IL byte code, but may change in the
future.
Users who want to benefit from incremental builds and who want to
compile both the project and its dependencies should use the
dotnet\-build(1) command.
.PP
The result of compilation is by default an executable file that can be
ran.
Output files, are written to the child \f[C]bin\f[] folder, which will
be created if it doesn\[aq]t exist.
Files will be overwritten as needed.
The temporary files that are created during compilation are placed in
the child \f[C]obj\f[] folder.
.PP
The executables also require a special configuration section in
project.json:
.IP
.nf
\f[C]
{\
\ \ \ \ "compilationOptions":\ {
\ \ \ \ \ \ "emitEntryPoint":\ true
\ \ \ \ }
}
\f[]
.fi
.PP
The default native [\-\-native] output is a native exe that conforms to
the architecture of the underlying operating system (i.e.
running on 64\-bit OS will produce a native 64\-bit exe).
This can be overriden via the \-\-arch switch and specifying the wanted
architecture.
The executable has a default extension of "" on Linux and OS X and
".exe" on Windows.
The source must include a static void main entry point, or it is an
error, unless otherwise specified in the project.json.
The dynamic library [dylib] output option has the default extension of
".so" on Linux/UNIX, ".dynlib" on OS X and ".dll" on Windows.
The static library [staticlib] option has the default extension of ".a"
on Linux, UNIX and OS X and ".lib" on Windows.
.PP
This command relies on the following artifacts: source files,
project.json project file and the "lock" file (project.lock.json).
Prior to invoking dotnet\-compile, dotnet\-restore(1) should be run to
restore any dependencies that are needed for the application.
.SH OPTIONS
.PP
\f[C]\-n,\ \-\-native\f[]
.IP
.nf
\f[C]
Compiles\ source\ to\ native\ machine\ code,\ for\ the\ local\ machine.\ The\ default\ is\ a\ native\ executable.\ The\ default\ executable\ extension\ is\ no\ extension\ and\ ".exe"\ on\ Windows.
\f[]
.fi
.PP
\f[C]\-t,\ \-\-temp\-output\ <PATH>\f[]
.IP
.nf
\f[C]
Path\ where\ to\ drop\ the\ temporary\ binaries\ that\ are\ produced\ during\ compile.\ By\ default,\ the\ temporary\ binaries\ are\ dropped\ in\ the\ `obj`\ directory\ in\ the\ directory\ where\ `project.json`\ files\ lives,\ that\ is,\ where\ the\ application\ lives.\ \
\f[]
.fi
.PP
\f[C]\-f,\ \-\-framework\ <FID>\f[]
.IP
.nf
\f[C]
Compile\ the\ application\ for\ the\ specified\ framework.\ If\ the\ framework\ is\ not\ specified,\ one\ specified\ in\ `project.json`\ will\ be\ used.\
\f[]
.fi
.PP
\f[C]\-c,\ \-\-configuration\ <CONFIGURATION>\f[]
.IP
.nf
\f[C]
Compile\ the\ application\ under\ the\ specified\ configuration.\ If\ not\ specified,\ the\ configuration\ will\ default\ to\ "Debug".\ \
\f[]
.fi
.PP
\f[C]\-o,\ \-\-output\ filename\f[]
.IP
.nf
\f[C]
Specifies\ the\ filename\ to\ be\ used.\ By\ default,\ the\ resulting\ filename\ will\ be\ the\ same\ as\ the\ project\ name\ specified\ in\ `project.json`,\ if\ one\ exists,\ or\ the\ directory\ in\ which\ the\ source\ files\ reside.\
\f[]
.fi
.PP
\f[C]\-\-no\-project\-dependencies\f[]
.IP
.nf
\f[C]
Skips\ building\ cross\-project\ references.\ The\ effect\ of\ this\ is\ that\ only\ the\ current\ project\ will\ be\ built.\
\f[]
.fi
.PP
\f[C]\-a,\ \-\-arch\f[]
.IP
.nf
\f[C]
The\ architecture\ for\ which\ to\ compile.\ x64\ only\ currently\ supported.
\f[]
.fi
.PP
\f[C]\-\-ilc\-args\ <ARGS>\f[]
.IP
.nf
\f[C]
Specified\ parameters\ are\ passed\ through\ to\ ILC\ and\ are\ used\ by\ the\ engine\ when\ doing\ native\ compilation.\
\f[]
.fi
.PP
\f[C]\-\-cpp\f[]
.IP
.nf
\f[C]
Specify\ the\ C++\ code\ generator\ to\ do\ native\ compilation\ of\ code\ instead\ of\ the\ default\ RyuJIT.\ \ \ \ \ \ \
\f[]
.fi
.PP
\f[C]\-v,\ \-\-verbose\f[]
.IP
.nf
\f[C]
Prints\ verbose\ logging\ information,\ to\ follow\ the\ flow\ of\ execution\ of\ the\ command.
\f[]
.fi
.PP
\f[C]\-h,\ \-\-help\f[]
.IP
.nf
\f[C]
Show\ short\ help.\
\f[]
.fi
.SH SEE ALSO
.PP
dotnet\-restore(1), dotnet\-publish(1), dotnet(1)
.SH AUTHORS
Zlatko Knezevic zlakne\@microsoft.com.

2
Documentation/manpages/sdk/dotnet-help.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet help command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy

2
Documentation/manpages/sdk/dotnet-install-script.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet\-install scripts" "1" "" "" ".NET Core"
.hy

6
Documentation/manpages/sdk/dotnet-list-reference.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet list reference command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -6,7 +6,7 @@
.PP
.SH NAME
.PP
\f[C]dotnet\ list\ reference\f[] \- Lists project to project references.
\f[C]dotnet\ list\ reference\f[] \- Lists project\-to\-project references.
.SH SYNOPSIS
.PP
\f[C]dotnet\ list\ [<PROJECT>]\ reference\ [\-h|\-\-help]\f[]
@ -18,7 +18,7 @@ The \f[C]dotnet\ list\ reference\f[] command provides a convenient option to lis
\f[C]PROJECT\f[]
.PP
Specifies the project file to use for listing references.
If not specified, the command will search the current directory for a project file.
If not specified, the command searches the current directory for a project file.
.SH OPTIONS
.PP
\f[C]\-h|\-\-help\f[]

55
Documentation/manpages/sdk/dotnet-migrate.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet migrate command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -8,8 +8,13 @@
.PP
\f[C]dotnet\ migrate\f[] \- Migrates a Preview 2 .NET Core project to a .NET Core SDK 1.0 project.
.SH SYNOPSIS
.PP
\f[C]dotnet\ migrate\ [<SOLUTION_FILE|PROJECT_DIR>]\ [\-t|\-\-template\-file]\ [\-v|\-\-sdk\-package\-version]\ [\-x|\-\-xproj\-file]\ [\-s|\-\-skip\-project\-references]\ [\-r|\-\-report\-file]\ [\-\-format\-report\-file\-json]\ [\-\-skip\-backup]\ [\-h|\-\-help]\f[]
.IP
.nf
\f[C]
dotnet\ migrate\ [<SOLUTION_FILE|PROJECT_DIR>]\ [\-\-format\-report\-file\-json]\ [\-r|\-\-report\-file]\ [\-s|\-\-skip\-project\-references]\ [\-\-skip\-backup]\ [\-t|\-\-template\-file]\ [\-v|\-\-sdk\-package\-version]\ [\-x|\-\-xproj\-file]
dotnet\ migrate\ [\-h|\-\-help]
\f[]
.fi
.SH DESCRIPTION
.PP
The \f[C]dotnet\ migrate\f[] command migrates a valid Preview 2 \f[I]project.json\f[]\-based project to a valid .NET Core SDK 1.0 \f[I]csproj\f[] project.
@ -17,7 +22,7 @@ The \f[C]dotnet\ migrate\f[] command migrates a valid Preview 2 \f[I]project.jso
By default, the command migrates the root project and any project references that the root project contains.
This behavior is disabled using the \f[C]\-\-skip\-project\-references\f[] option at runtime.
.PP
Migration is performed on the following:
Migration can be performed on the following assets:
.IP \[bu] 2
A single project by specifying the \f[I]project.json\f[] file to migrate.
.IP \[bu] 2
@ -25,7 +30,7 @@ All of the directories specified in the \f[I]global.json\f[] file by passing in
.IP \[bu] 2
A \f[I]solution.sln\f[] file, where it migrates the projects referenced in the solution.
.IP \[bu] 2
On all sub\-directories of the given directory recursively.
On all subdirectories of the given directory recursively.
.PP
The \f[C]dotnet\ migrate\f[] command keeps the migrated \f[I]project.json\f[] file inside a \f[C]backup\f[] directory, which it creates if the directory doesn't exist.
This behavior is overridden using the \f[C]\-\-skip\-backup\f[] option.
@ -44,19 +49,36 @@ The path to one of the following:
.IP \[bu] 2
a \f[I]project.json\f[] file to migrate.
.IP \[bu] 2
a \f[I]global.json\f[] file, it will migrate the folders specified in \f[I]global.json\f[].
a \f[I]global.json\f[] file: the folders specified in \f[I]global.json\f[] are migrated.
.IP \[bu] 2
a \f[I]solution.sln\f[] file, it will migrate the projects referenced in the solution.
a \f[I]solution.sln\f[] file: the projects referenced in the solution are migrated.
.IP \[bu] 2
a directory to migrate, it will recursively search for \f[I]project.json\f[] files to migrate.
a directory to migrate: recursively searches for \f[I]project.json\f[] files to migrate inside the specified directory.
.PP
Defaults to current directory if nothing is specified.
.SH OPTIONS
.PP
\f[C]\-\-format\-report\-file\-json\ <REPORT_FILE>\f[]
.PP
Output migration report file as JSON rather than user messages.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-r|\-\-report\-file\ <REPORT_FILE>\f[]
.PP
Output migration report to a file in addition to the console.
.PP
\f[C]\-s|\-\-skip\-project\-references\ [Debug|Release]\f[]
.PP
Skip migrating project references.
By default, project references are migrated recursively.
.PP
\f[C]\-\-skip\-backup\f[]
.PP
Skip moving \f[I]project.json\f[], \f[I]global.json\f[], and \f[I]*.xproj\f[] to a \f[C]backup\f[] directory after successful migration.
.PP
\f[C]\-t|\-\-template\-file\ <TEMPLATE_FILE>\f[]
.PP
Template csproj file to use for migration.
@ -71,23 +93,6 @@ The default is the version of the SDK in \f[C]dotnet\ new\f[].
.PP
The path to the xproj file to use.
Required when there is more than one xproj in a project directory.
.PP
\f[C]\-s|\-\-skip\-project\-references\ [Debug|Release]\f[]
.PP
Skip migrating project references.
By default, project references are migrated recursively.
.PP
\f[C]\-r|\-\-report\-file\ <REPORT_FILE>\f[]
.PP
Output migration report to a file in addition to the console.
.PP
\f[C]\-\-format\-report\-file\-json\ <REPORT_FILE>\f[]
.PP
Output migration report file as JSON rather than user messages.
.PP
\f[C]\-\-skip\-backup\f[]
.PP
Skip moving \f[I]project.json\f[], \f[I]global.json\f[], and \f[I]*.xproj\f[] to a \f[C]backup\f[] directory after successful migration.
.SH EXAMPLES
.PP
Migrate a project in the current directory and all of its project\-to\-project dependencies:

4
Documentation/manpages/sdk/dotnet-msbuild.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet msbuild command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -16,7 +16,7 @@ The \f[C]dotnet\ msbuild\f[] command allows access to a fully functional MSBuild
.PP
The command has the exact same capabilities as existing MSBuild command\-line client.
The options are all the same.
Use the MSBuild Command\-Line Reference to obtain information on the available options.
For more information about the available options, see the MSBuild Command\-Line Reference.
.SH EXAMPLES
.PP
Build a project and its dependencies:

415
Documentation/manpages/sdk/dotnet-new.1
View file

@ -1,5 +1,5 @@
.\"t
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet new command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -9,6 +9,16 @@
.PP
\f[C]dotnet\ new\f[] \- Creates a new project, configuration file, or solution based on the specified template.
.SH SYNOPSIS
.SS .NET Core 2.1
.IP
.nf
\f[C]
dotnet\ new\ <TEMPLATE>\ [\-\-force]\ [\-i|\-\-install]\ [\-lang|\-\-language]\ [\-n|\-\-name]\ [\-\-nuget\-source]\ [\-o|\-\-output]
\ \ \ \ [\-u|\-\-uninstall]\ [Template\ options]
dotnet\ new\ <TEMPLATE>\ [\-l|\-\-list]\ [\-\-type]
dotnet\ new\ [\-h|\-\-help]
\f[]
.fi
.SS .NET Core 2.0
.IP
.nf
@ -42,11 +52,159 @@ The command calls the template engine to create the artifacts on disk based on t
The template to instantiate when the command is invoked.
Each template might have specific options you can pass.
For more information, see Template options.
.SS .NET Core 2.1
.PP
The command contains a default list of templates.
Use \f[C]dotnet\ new\ \-l\f[] to obtain a list of the available templates.
The following table shows the templates that come pre\-installed with the .NET Core SDK 2.1.300.
The default language for the template is shown inside the brackets.
.PP
.TS
tab(@);
l l l.
T{
Template description
T}@T{
Template name
T}@T{
Languages
T}
_
T{
Console application
T}@T{
\f[C]console\f[]
T}@T{
[C#], F#, VB
T}
T{
Class library
T}@T{
\f[C]classlib\f[]
T}@T{
[C#], F#, VB
T}
T{
Unit test project
T}@T{
\f[C]mstest\f[]
T}@T{
[C#], F#, VB
T}
T{
xUnit test project
T}@T{
\f[C]xunit\f[]
T}@T{
[C#], F#, VB
T}
T{
Razor page
T}@T{
\f[C]page\f[]
T}@T{
[C#]
T}
T{
MVC ViewImports
T}@T{
\f[C]viewimports\f[]
T}@T{
[C#]
T}
T{
MVC ViewStart
T}@T{
\f[C]viewstart\f[]
T}@T{
[C#]
T}
T{
ASP.NET Core empty
T}@T{
\f[C]web\f[]
T}@T{
[C#], F#
T}
T{
ASP.NET Core Web App (Model\-View\-Controller)
T}@T{
\f[C]mvc\f[]
T}@T{
[C#], F#
T}
T{
ASP.NET Core Web App
T}@T{
\f[C]razor\f[]
T}@T{
[C#]
T}
T{
ASP.NET Core with Angular
T}@T{
\f[C]angular\f[]
T}@T{
[C#]
T}
T{
ASP.NET Core with React.js
T}@T{
\f[C]react\f[]
T}@T{
[C#]
T}
T{
ASP.NET Core with React.js and Redux
T}@T{
\f[C]reactredux\f[]
T}@T{
[C#]
T}
T{
ASP.NET Core Web API
T}@T{
\f[C]webapi\f[]
T}@T{
[C#], F#
T}
T{
Razor class library
T}@T{
\f[C]razorclasslib\f[]
T}@T{
[C#]
T}
T{
global.json file
T}@T{
\f[C]globaljson\f[]
T}@T{
T}
T{
NuGet config
T}@T{
\f[C]nugetconfig\f[]
T}@T{
T}
T{
Web config
T}@T{
\f[C]webconfig\f[]
T}@T{
T}
T{
Solution file
T}@T{
\f[C]sln\f[]
T}@T{
T}
.TE
.SS .NET Core 2.0
.PP
The command contains a default list of templates.
Use \f[C]dotnet\ new\ \-l\f[] to obtain a list of the available templates.
The following table shows the templates that come pre\-installed with the .NET Core 2.0 SDK.
The following table shows the templates that come pre\-installed with the .NET Core SDK 2.0.
The default language for the template is shown inside the brackets.
.PP
.TS
@ -144,7 +302,7 @@ T}@T{
T}@T{
T}
T{
Nuget config
NuGet config
T}@T{
\f[C]nugetconfig\f[]
T}@T{
@ -184,7 +342,7 @@ T}
.PP
The command contains a default list of templates.
Use \f[C]dotnet\ new\ \-all\f[] to obtain a list of the available templates.
The following table shows the templates that come pre\-installed with the .NET Core 1.x SDK.
The following table shows the templates that come pre\-installed with the .NET Core SDK 1.x.
The default language for the template is shown inside the brackets.
.PP
.TS
@ -248,7 +406,7 @@ T}@T{
[C#]
T}
T{
Nuget config
NuGet config
T}@T{
\f[C]nugetconfig\f[]
T}@T{
@ -269,6 +427,74 @@ T}
.PP
* * * * *
.SH OPTIONS
.SS .NET Core 2.1
.PP
\f[C]\-\-force\f[]
.PP
Forces content to be generated even if it would change existing files.
This is required when the output directory already contains a project.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out help for the command.
It can be invoked for the \f[C]dotnet\ new\f[] command itself or for any template, such as \f[C]dotnet\ new\ mvc\ \-\-help\f[].
.PP
\f[C]\-i|\-\-install\ <PATH|NUGET_ID>\f[]
.PP
Installs a source or template pack from the \f[C]PATH\f[] or \f[C]NUGET_ID\f[] provided.
If you want to install a prerelease version of a template package, you need to specify the version in the format of \f[C]<package\-name>::<package\-version>\f[].
By default, \f[C]dotnet\ new\f[] passes * for the version, which represents the last stable package version.
See an example at the Examples section.
.PP
For information on creating custom templates, see Custom templates for dotnet new.
.PP
\f[C]\-l|\-\-list\f[]
.PP
Lists templates containing the specified name.
If invoked for the \f[C]dotnet\ new\f[] command, it lists the possible templates available for the given directory.
For example if the directory already contains a project, it doesn't list all project templates.
.PP
\f[C]\-lang|\-\-language\ {C#|F#|VB}\f[]
.PP
The language of the template to create.
The language accepted varies by the template (see defaults in the arguments section).
Not valid for some templates.
.IP
.nf
\f[C]
>\ [!NOTE]
>\ Some\ shells\ interpret\ `#`\ as\ a\ special\ character.\ In\ those\ cases,\ you\ need\ to\ enclose\ the\ language\ parameter\ value,\ such\ as\ `dotnet\ new\ console\ \-lang\ "F#"`.
\f[]
.fi
.PP
\f[C]\-n|\-\-name\ <OUTPUT_NAME>\f[]
.PP
The name for the created output.
If no name is specified, the name of the current directory is used.
.PP
\f[C]\-\-nuget\-source\f[]
.PP
Specifies a NuGet source to use during install.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
Location to place the generated output.
The default is the current directory.
.PP
\f[C]\-\-type\f[]
.PP
Filters templates based on available types.
Predefined values are \[lq]project\[rq], \[lq]item\[rq] or \[lq]other\[rq].
.PP
\f[C]\-u|\-\-uninstall\ <PATH|NUGET_ID>\f[]
.PP
Uninstalls a source or template pack at the \f[C]PATH\f[] or \f[C]NUGET_ID\f[] provided.
.RS
.PP
[!NOTE] To uninstall a template using a \f[C]PATH\f[], you need to fully qualify the path.
For example, \f[I]C:/Users/<USER>/Documents/Templates/GarciaSoftware.ConsoleTemplate.CSharp\f[] will work, but \f[I]./GarciaSoftware.ConsoleTemplate.CSharp\f[] from the containing folder will not.
Additionally, do not include a final terminating directory slash on your template path.
.RE
.SS .NET Core 2.0
.PP
\f[C]\-\-force\f[]
@ -380,11 +606,11 @@ The default is the current directory.
.PP
Each project template may have additional options available.
The core templates have the following additional options:
.SS .NET Core 2.0
.SS .NET Core 2.1
.PP
\f[B]console, angular, react, reactredux\f[]
\f[B]console, angular, react, reactredux, razorclasslib\f[]
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't perform an implicit restore during project creation.
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]classlib\f[]
.PP
@ -392,13 +618,13 @@ The core templates have the following additional options:
Values: \f[C]netcoreapp2.0\f[] to create a .NET Core Class Library or \f[C]netstandard2.0\f[] to create a .NET Standard Class Library.
The default value is \f[C]netstandard2.0\f[].
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't perform an implicit restore during project creation.
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]mstest, xunit\f[]
.PP
\f[C]\-p|\-\-enable\-pack\f[] \- Enables packaging for the project using dotnet pack.
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't perform an implicit restore during project creation.
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]globaljson\f[]
.PP
@ -408,7 +634,7 @@ The default value is \f[C]netstandard2.0\f[].
.PP
\f[C]\-\-use\-launch\-settings\f[] \- Includes \f[I]launchSettings.json\f[] in the generated template output.
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't perform an implicit restore during project creation.
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]webapi\f[]
.PP
@ -454,7 +680,7 @@ Only applies to \f[C]SingleOrg\f[] or \f[C]MultiOrg\f[] authentication.
\f[C]\-uld|\-\-use\-local\-db\f[] \- Specifies LocalDB should be used instead of SQLite.
Only applies to \f[C]Individual\f[] or \f[C]IndividualB2C\f[] authentication.
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't perform an implicit restore during project creation.
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]mvc, razor\f[]
.PP
@ -475,7 +701,7 @@ The possible values are:
.PP
\f[C]\-\-aad\-b2c\-instance\ <INSTANCE>\f[] \- The Azure Active Directory B2C instance to connect to.
Use with \f[C]IndividualB2C\f[] authentication.
The default value is \f[C]https://login.microsoftonline.com/tfp/\f[] .
The default value is \f[C]https://login.microsoftonline.com/tfp/\f[].
.PP
\f[C]\-ssp|\-\-susi\-policy\-id\ <ID>\f[] \- The sign\-in and sign\-up policy ID for this project.
Use with \f[C]IndividualB2C\f[] authentication.
@ -495,15 +721,15 @@ Use with \f[C]IndividualB2C\f[], \f[C]SingleOrg\f[], or \f[C]MultiOrg\f[] authen
The default value is \f[C]11111111\-1111\-1111\-11111111111111111\f[].
.PP
\f[C]\-\-domain\ <DOMAIN>\f[] \- The domain for the directory tenant.
Use with \f[C]SingleOrg\f[] or \f[C]IndividualB2C\f[] authentication..
Use with \f[C]SingleOrg\f[] or \f[C]IndividualB2C\f[] authentication.
The default value is \f[C]qualified.domain.name\f[].
.PP
\f[C]\-\-tenant\-id\ <ID>\f[] \- The TenantId ID of the directory to connect to.
Use with \f[C]SingleOrg\f[] authentication..
Use with \f[C]SingleOrg\f[] authentication.
The default value is \f[C]22222222\-2222\-2222\-2222\-222222222222\f[].
.PP
\f[C]\-\-callback\-path\ <PATH>\f[] \- The request path within the application's base path of the redirect URI.
Use with \f[C]SingleOrg\f[] or \f[C]IndividualB2C\f[] authentication..
Use with \f[C]SingleOrg\f[] or \f[C]IndividualB2C\f[] authentication.
The default value is \f[C]/signin\-oidc\f[].
.PP
\f[C]\-r|\-\-org\-read\-access\f[] \- Allows this application read\-access to the directory.
@ -516,7 +742,156 @@ Only applies to \f[C]SingleOrg\f[] or \f[C]MultiOrg\f[] authentication.
\f[C]\-uld|\-\-use\-local\-db\f[] \- Specifies LocalDB should be used instead of SQLite.
Only applies to \f[C]Individual\f[] or \f[C]IndividualB2C\f[] authentication.
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't perform an implicit restore during project creation.
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]page\f[]
.PP
\f[C]\-na|\-\-namespace\ <NAMESPACE_NAME>\f[]\- Namespace for the generated code.
The default value is \f[C]MyApp.Namespace\f[].
.PP
\f[C]\-np|\-\-no\-pagemodel\f[] \- Creates the page without a PageModel.
.PP
\f[B]viewimports\f[]
.PP
\f[C]\-na|\-\-namespace\ <NAMESPACE_NAME>\f[]\- Namespace for the generated code.
The default value is \f[C]MyApp.Namespace\f[].
.SS .NET Core 2.0
.PP
\f[B]console, angular, react, reactredux\f[]
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]classlib\f[]
.PP
\f[C]\-f|\-\-framework\ <FRAMEWORK>\f[] \- Specifies the framework to target.
Values: \f[C]netcoreapp2.0\f[] to create a .NET Core Class Library or \f[C]netstandard2.0\f[] to create a .NET Standard Class Library.
The default value is \f[C]netstandard2.0\f[].
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]mstest, xunit\f[]
.PP
\f[C]\-p|\-\-enable\-pack\f[] \- Enables packaging for the project using dotnet pack.
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]globaljson\f[]
.PP
\f[C]\-\-sdk\-version\ <VERSION_NUMBER>\f[] \- Specifies the version of the .NET Core SDK to use in the \f[I]global.json\f[] file.
.PP
\f[B]web\f[]
.PP
\f[C]\-\-use\-launch\-settings\f[] \- Includes \f[I]launchSettings.json\f[] in the generated template output.
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]webapi\f[]
.PP
\f[C]\-au|\-\-auth\ <AUTHENTICATION_TYPE>\f[] \- The type of authentication to use.
The possible values are:
.IP \[bu] 2
\f[C]None\f[] \- No authentication (Default).
.IP \[bu] 2
\f[C]IndividualB2C\f[] \- Individual authentication with Azure AD B2C.
.IP \[bu] 2
\f[C]SingleOrg\f[] \- Organizational authentication for a single tenant.
.IP \[bu] 2
\f[C]Windows\f[] \- Windows authentication.
.PP
\f[C]\-\-aad\-b2c\-instance\ <INSTANCE>\f[] \- The Azure Active Directory B2C instance to connect to.
Use with \f[C]IndividualB2C\f[] authentication.
The default value is \f[C]https://login.microsoftonline.com/tfp/\f[].
.PP
\f[C]\-ssp|\-\-susi\-policy\-id\ <ID>\f[] \- The sign\-in and sign\-up policy ID for this project.
Use with \f[C]IndividualB2C\f[] authentication.
.PP
\f[C]\-\-aad\-instance\ <INSTANCE>\f[] \- The Azure Active Directory instance to connect to.
Use with \f[C]SingleOrg\f[] authentication.
The default value is \f[C]https://login.microsoftonline.com/\f[].
.PP
\f[C]\-\-client\-id\ <ID>\f[] \- The Client ID for this project.
Use with \f[C]IndividualB2C\f[] or \f[C]SingleOrg\f[] authentication.
The default value is \f[C]11111111\-1111\-1111\-11111111111111111\f[].
.PP
\f[C]\-\-domain\ <DOMAIN>\f[] \- The domain for the directory tenant.
Use with \f[C]SingleOrg\f[] or \f[C]IndividualB2C\f[] authentication.
The default value is \f[C]qualified.domain.name\f[].
.PP
\f[C]\-\-tenant\-id\ <ID>\f[] \- The TenantId ID of the directory to connect to.
Use with \f[C]SingleOrg\f[] authentication.
The default value is \f[C]22222222\-2222\-2222\-2222\-222222222222\f[].
.PP
\f[C]\-r|\-\-org\-read\-access\f[] \- Allows this application read\-access to the directory.
Only applies to \f[C]SingleOrg\f[] or \f[C]MultiOrg\f[] authentication.
.PP
\f[C]\-\-use\-launch\-settings\f[] \- Includes \f[I]launchSettings.json\f[] in the generated template output.
.PP
\f[C]\-uld|\-\-use\-local\-db\f[] \- Specifies LocalDB should be used instead of SQLite.
Only applies to \f[C]Individual\f[] or \f[C]IndividualB2C\f[] authentication.
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]mvc, razor\f[]
.PP
\f[C]\-au|\-\-auth\ <AUTHENTICATION_TYPE>\f[] \- The type of authentication to use.
The possible values are:
.IP \[bu] 2
\f[C]None\f[] \- No authentication (Default).
.IP \[bu] 2
\f[C]Individual\f[] \- Individual authentication.
.IP \[bu] 2
\f[C]IndividualB2C\f[] \- Individual authentication with Azure AD B2C.
.IP \[bu] 2
\f[C]SingleOrg\f[] \- Organizational authentication for a single tenant.
.IP \[bu] 2
\f[C]MultiOrg\f[] \- Organizational authentication for multiple tenants.
.IP \[bu] 2
\f[C]Windows\f[] \- Windows authentication.
.PP
\f[C]\-\-aad\-b2c\-instance\ <INSTANCE>\f[] \- The Azure Active Directory B2C instance to connect to.
Use with \f[C]IndividualB2C\f[] authentication.
The default value is \f[C]https://login.microsoftonline.com/tfp/\f[].
.PP
\f[C]\-ssp|\-\-susi\-policy\-id\ <ID>\f[] \- The sign\-in and sign\-up policy ID for this project.
Use with \f[C]IndividualB2C\f[] authentication.
.PP
\f[C]\-rp|\-\-reset\-password\-policy\-id\ <ID>\f[] \- The reset password policy ID for this project.
Use with \f[C]IndividualB2C\f[] authentication.
.PP
\f[C]\-ep|\-\-edit\-profile\-policy\-id\ <ID>\f[] \- The edit profile policy ID for this project.
Use with \f[C]IndividualB2C\f[] authentication.
.PP
\f[C]\-\-aad\-instance\ <INSTANCE>\f[] \- The Azure Active Directory instance to connect to.
Use with \f[C]SingleOrg\f[] or \f[C]MultiOrg\f[] authentication.
The default value is \f[C]https://login.microsoftonline.com/\f[].
.PP
\f[C]\-\-client\-id\ <ID>\f[] \- The Client ID for this project.
Use with \f[C]IndividualB2C\f[], \f[C]SingleOrg\f[], or \f[C]MultiOrg\f[] authentication.
The default value is \f[C]11111111\-1111\-1111\-11111111111111111\f[].
.PP
\f[C]\-\-domain\ <DOMAIN>\f[] \- The domain for the directory tenant.
Use with \f[C]SingleOrg\f[] or \f[C]IndividualB2C\f[] authentication.
The default value is \f[C]qualified.domain.name\f[].
.PP
\f[C]\-\-tenant\-id\ <ID>\f[] \- The TenantId ID of the directory to connect to.
Use with \f[C]SingleOrg\f[] authentication.
The default value is \f[C]22222222\-2222\-2222\-2222\-222222222222\f[].
.PP
\f[C]\-\-callback\-path\ <PATH>\f[] \- The request path within the application's base path of the redirect URI.
Use with \f[C]SingleOrg\f[] or \f[C]IndividualB2C\f[] authentication.
The default value is \f[C]/signin\-oidc\f[].
.PP
\f[C]\-r|\-\-org\-read\-access\f[] \- Allows this application read\-access to the directory.
Only applies to \f[C]SingleOrg\f[] or \f[C]MultiOrg\f[] authentication.
.PP
\f[C]\-\-use\-launch\-settings\f[] \- Includes \f[I]launchSettings.json\f[] in the generated template output.
.PP
\f[C]\-\-use\-browserlink\f[] \- Includes BrowserLink in the project.
.PP
\f[C]\-uld|\-\-use\-local\-db\f[] \- Specifies LocalDB should be used instead of SQLite.
Only applies to \f[C]Individual\f[] or \f[C]IndividualB2C\f[] authentication.
.PP
\f[C]\-\-no\-restore\f[] \- Doesn't execute an implicit restore during project creation.
.PP
\f[B]page\f[]
.PP
@ -564,7 +939,7 @@ Create an F# console application project in the current directory:
.PP
\f[C]dotnet\ new\ console\ \-lang\ F#\f[]
.PP
Create a .NET Standard class library project in the specified directory (available only with .NET Core 2.0 SDK or later versions):
Create a .NET Standard class library project in the specified directory (available only with .NET Core SDK 2.0 or later versions):
.PP
\f[C]dotnet\ new\ classlib\ \-lang\ VB\ \-o\ MyLibrary\f[]
.PP
@ -583,6 +958,10 @@ List all templates available for MVC:
Install version 2.0 of the Single Page Application templates for ASP.NET Core (command option available for .NET Core SDK 1.1 and later versions only):
.PP
\f[C]dotnet\ new\ \-i\ Microsoft.DotNet.Web.Spa.ProjectTemplates::2.0.0\f[]
.PP
Create a \f[I]global.json\f[] in the current directory setting the SDK version to 2.0.0 (available only with .NET Core SDK 2.0 or later versions):
.PP
\f[C]dotnet\ new\ globaljson\ \-\-sdk\-version\ 2.0.0\f[]
.SS See also
.PP
Custom templates for dotnet new

94
Documentation/manpages/sdk/dotnet-nuget-delete.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet nuget delete command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -8,8 +8,35 @@
.PP
\f[C]dotnet\ nuget\ delete\f[] \- Deletes or unlists a package from the server.
.SH SYNOPSIS
.SS .NET Core 2.1
.IP
.nf
\f[C]
dotnet\ nuget\ delete\ [<PACKAGE_NAME>\ <PACKAGE_VERSION>]\ [\-\-force\-english\-output]\ [\-k|\-\-api\-key]\ [\-\-no\-service\-endpoint]
\ \ \ \ [\-\-non\-interactive]\ [\-s|\-\-source]
dotnet\ nuget\ delete\ [\-h|\-\-help]
\f[]
.fi
.SS .NET Core 2.0
.IP
.nf
\f[C]
dotnet\ nuget\ delete\ [<PACKAGE_NAME>\ <PACKAGE_VERSION>]\ [\-\-force\-english\-output]\ [\-k|\-\-api\-key]\ [\-\-non\-interactive]
\ \ \ \ [\-s|\-\-source]
dotnet\ nuget\ delete\ [\-h|\-\-help]
\f[]
.fi
.SS .NET Core 1.x
.IP
.nf
\f[C]
dotnet\ nuget\ delete\ [<PACKAGE_NAME>\ <PACKAGE_VERSION>]\ [\-\-force\-english\-output]\ [\-k|\-\-api\-key]\ [\-\-non\-interactive]
\ \ \ \ [\-s|\-\-source]
dotnet\ nuget\ delete\ [\-h|\-\-help]
\f[]
.fi
.PP
\f[C]dotnet\ nuget\ delete\ [<PACKAGE_NAME>\ <PACKAGE_VERSION>]\ [\-s|\-\-source]\ [\-\-non\-interactive]\ [\-k|\-\-api\-key]\ [\-\-force\-english\-output]\ [\-h|\-\-help]\f[]
* * * * *
.SH DESCRIPTION
.PP
The \f[C]dotnet\ nuget\ delete\f[] command deletes or unlists a package from the server.
@ -18,34 +45,85 @@ For nuget.org, the action is to unlist the package.
.PP
\f[C]PACKAGE_NAME\f[]
.PP
Package to delete.
Name/ID of the package to delete.
.PP
\f[C]PACKAGE_VERSION\f[]
.PP
Version of the package to delete.
.SH OPTIONS
.SS .NET Core 2.1
.PP
\f[C]\-\-force\-english\-output\f[]
.PP
Forces the application to run using an invariant, English\-based culture.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-s|\-\-source\ <SOURCE>\f[]
\f[C]\-k|\-\-api\-key\ <API_KEY>\f[]
.PP
Specifies the server URL.
Supported URLs for nuget.org include \f[C]http://www.nuget.org\f[], \f[C]http://www.nuget.org/api/v3\f[], and \f[C]http://www.nuget.org/api/v2/package\f[].
For private feeds, substitute the host name (for example, \f[C]%hostname%/api/v3\f[]).
The API key for the server.
.PP
\f[C]\-\-no\-service\-endpoint\f[] Doesn't append \[lq]api/v2/packages\[rq] to the source URL.
.PP
\f[C]\-\-non\-interactive\f[]
.PP
Doesn't prompt for user input or confirmations.
.PP
\f[C]\-s|\-\-source\ <SOURCE>\f[]
.PP
Specifies the server URL.
Supported URLs for nuget.org include \f[C]http://www.nuget.org\f[], \f[C]http://www.nuget.org/api/v3\f[], and \f[C]http://www.nuget.org/api/v2/package\f[].
For private feeds, replace the host name (for example, \f[C]%hostname%/api/v3\f[]).
.SS .NET Core 2.0
.PP
\f[C]\-\-force\-english\-output\f[]
.PP
Forces the application to run using an invariant, English\-based culture.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-k|\-\-api\-key\ <API_KEY>\f[]
.PP
The API key for the server.
.PP
\f[C]\-\-non\-interactive\f[]
.PP
Doesn't prompt for user input or confirmations.
.PP
\f[C]\-s|\-\-source\ <SOURCE>\f[]
.PP
Specifies the server URL.
Supported URLs for nuget.org include \f[C]http://www.nuget.org\f[], \f[C]http://www.nuget.org/api/v3\f[], and \f[C]http://www.nuget.org/api/v2/package\f[].
For private feeds, replace the host name (for example, \f[C]%hostname%/api/v3\f[]).
.SS .NET Core 1.x
.PP
\f[C]\-\-force\-english\-output\f[]
.PP
Forces command\-line output in English.
Forces the application to run using an invariant, English\-based culture.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-k|\-\-api\-key\ <API_KEY>\f[]
.PP
The API key for the server.
.PP
\f[C]\-\-non\-interactive\f[]
.PP
Doesn't prompt for user input or confirmations.
.PP
\f[C]\-s|\-\-source\ <SOURCE>\f[]
.PP
Specifies the server URL.
Supported URLs for nuget.org include \f[C]http://www.nuget.org\f[], \f[C]http://www.nuget.org/api/v3\f[], and \f[C]http://www.nuget.org/api/v2/package\f[].
For private feeds, replace the host name (for example, \f[C]%hostname%/api/v3\f[]).
.PP
* * * * *
.SH EXAMPLES
.PP
Deletes version 1.0 of package \f[C]Microsoft.AspNetCore.Mvc\f[]:

32
Documentation/manpages/sdk/dotnet-nuget-locals.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet nuget locals command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -8,8 +8,13 @@
.PP
\f[C]dotnet\ nuget\ locals\f[] \- Clears or lists local NuGet resources.
.SH SYNOPSIS
.PP
\f[C]dotnet\ nuget\ locals\ <CACHE_LOCATION>\ [(\-c|\-\-clear)|(\-l|\-\-list)]\ [\-\-force\-english\-output]\ [\-h|\-\-help]\f[]
.IP
.nf
\f[C]
dotnet\ nuget\ locals\ <CACHE_LOCATION>\ [(\-c|\-\-clear)|(\-l|\-\-list)]\ [\-\-force\-english\-output]
dotnet\ nuget\ locals\ [\-h|\-\-help]
\f[]
.fi
.SH DESCRIPTION
.PP
The \f[C]dotnet\ nuget\ locals\f[] command clears or lists local NuGet resources in the http\-request cache, temporary cache, or machine\-wide global packages folder.
@ -17,38 +22,39 @@ The \f[C]dotnet\ nuget\ locals\f[] command clears or lists local NuGet resources
.PP
\f[C]CACHE_LOCATION\f[]
.PP
One of the following values:
The cache location to list or clear.
It accepts one of the following values:
.IP \[bu] 2
\f[C]all\f[] \- Indicates that the specified operation is applied to all cache types: http\-request cache, global packages cache, and the temporary cache.
.IP \[bu] 2
\f[C]http\-cache\f[] \- Indicates that the specified operation is applied only to the http\-request cache.
The other cache locations are not affected.
The other cache locations aren't affected.
.IP \[bu] 2
\f[C]global\-packages\f[] \- Indicates that the specified operation is applied only to the global packages cache.
The other cache locations are not affected.
The other cache locations aren't affected.
.IP \[bu] 2
\f[C]temp\f[] \- Indicates that the specified operation is applied only to the temporary cache.
The other cache locations are not affected.
The other cache locations aren't affected.
.SH OPTIONS
.PP
\f[C]\-\-force\-english\-output\f[]
.PP
Forces the application to run using an invariant, English\-based culture.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-c|\-\-clear\f[]
.PP
The clear option performs a clear operation on the specified cache type.
The clear option executes a clear operation on the specified cache type.
The contents of the cache directories are deleted recursively.
The executing user/group must have permission to the files in the cache directories.
If not, an error is displayed indicating the files/folders which were not cleared.
If not, an error is displayed indicating the files/folders that weren't cleared.
.PP
\f[C]\-l|\-\-list\f[]
.PP
The list option is used to display the location of the specified cache type.
.PP
\f[C]\-\-force\-english\-output\f[]
.PP
Forces command\-line output in English.
.SH EXAMPLES
.PP
Displays the paths of all the local cache directories (http\-cache directory, global\-packages cache directory, and temporary cache directory):

164
Documentation/manpages/sdk/dotnet-nuget-push.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet nuget push command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -8,8 +8,35 @@
.PP
\f[C]dotnet\ nuget\ push\f[] \- Pushes a package to the server and publishes it.
.SH SYNOPSIS
.SS .NET Core 2.1
.IP
.nf
\f[C]
dotnet\ nuget\ push\ [<ROOT>]\ [\-d|\-\-disable\-buffering]\ [\-\-force\-english\-output]\ [\-k|\-\-api\-key]\ [\-n|\-\-no\-symbols]
\ \ \ \ [\-\-no\-service\-endpoint]\ [\-s|\-\-source]\ [\-sk|\-\-symbol\-api\-key]\ [\-ss|\-\-symbol\-source]\ [\-t|\-\-timeout]
dotnet\ nuget\ push\ [\-h|\-\-help]
\f[]
.fi
.SS .NET Core 2.0
.IP
.nf
\f[C]
dotnet\ nuget\ push\ [<ROOT>]\ [\-d|\-\-disable\-buffering]\ [\-\-force\-english\-output]\ [\-k|\-\-api\-key]\ [\-n|\-\-no\-symbols]
\ \ \ \ [\-s|\-\-source]\ [\-sk|\-\-symbol\-api\-key]\ [\-ss|\-\-symbol\-source]\ [\-t|\-\-timeout]
dotnet\ nuget\ push\ [\-h|\-\-help]
\f[]
.fi
.SS .NET Core 1.x
.IP
.nf
\f[C]
dotnet\ nuget\ push\ [<ROOT>]\ [\-d|\-\-disable\-buffering]\ [\-\-force\-english\-output]\ [\-k|\-\-api\-key]\ [\-n|\-\-no\-symbols]
\ \ \ \ [\-s|\-\-source]\ [\-sk|\-\-symbol\-api\-key]\ [\-ss|\-\-symbol\-source]\ [\-t|\-\-timeout]
dotnet\ nuget\ push\ [\-h|\-\-help]
\f[]
.fi
.PP
\f[C]dotnet\ nuget\ push\ [<ROOT>]\ [\-s|\-\-source]\ [\-ss|\-\-symbol\-source]\ [\-t|\-\-timeout]\ [\-k|\-\-api\-key]\ [\-sk|\-\-symbol\-api\-key]\ [\-d|\-\-disable\-buffering]\ [\-n|\-\-no\-symbols]\ [\-\-force\-english\-output]\ [\-h|\-\-help]\f[]
* * * * *
.SH DESCRIPTION
.PP
The \f[C]dotnet\ nuget\ push\f[] command pushes a package to the server and publishes it.
@ -22,17 +49,122 @@ NuGet's default configuration is obtained by loading \f[I]%AppData%.config\f[] (
.PP
Specifies the file path to the package to be pushed.
.SH OPTIONS
.SS .NET Core 2.1
.PP
\f[C]\-d|\-\-disable\-buffering\f[]
.PP
Disables buffering when pushing to an HTTP(S) server to reduce memory usage.
.PP
\f[C]\-\-force\-english\-output\f[]
.PP
Forces the application to run using an invariant, English\-based culture.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-k|\-\-api\-key\ <API_KEY>\f[]
.PP
The API key for the server.
.PP
\f[C]\-n|\-\-no\-symbols\f[]
.PP
Doesn't push symbols (even if present).
.PP
\f[C]\-\-no\-service\-endpoint\f[]
.PP
Doesn't append \[lq]api/v2/packages\[rq] to the source URL.
.PP
\f[C]\-s|\-\-source\ <SOURCE>\f[]
.PP
Specifies the server URL.
This option is required unless \f[C]DefaultPushSource\f[] config value is set in the NuGet config file.
.PP
\f[C]\-\-symbol\-source\ <SOURCE>\f[]
\f[C]\-sk|\-\-symbol\-api\-key\ <API_KEY>\f[]
.PP
The API key for the symbol server.
.PP
\f[C]\-ss|\-\-symbol\-source\ <SOURCE>\f[]
.PP
Specifies the symbol server URL.
.PP
\f[C]\-t|\-\-timeout\ <TIMEOUT>\f[]
.PP
Specifies the timeout for pushing to a server in seconds.
Defaults to 300 seconds (5 minutes).
Specifying 0 (zero seconds) applies the default value.
.SS .NET Core 2.0
.PP
\f[C]\-d|\-\-disable\-buffering\f[]
.PP
Disables buffering when pushing to an HTTP(S) server to reduce memory usage.
.PP
\f[C]\-\-force\-english\-output\f[]
.PP
Forces the application to run using an invariant, English\-based culture.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-k|\-\-api\-key\ <API_KEY>\f[]
.PP
The API key for the server.
.PP
\f[C]\-n|\-\-no\-symbols\f[]
.PP
Doesn't push symbols (even if present).
.PP
\f[C]\-s|\-\-source\ <SOURCE>\f[]
.PP
Specifies the server URL.
This option is required unless \f[C]DefaultPushSource\f[] config value is set in the NuGet config file.
.PP
\f[C]\-sk|\-\-symbol\-api\-key\ <API_KEY>\f[]
.PP
The API key for the symbol server.
.PP
\f[C]\-ss|\-\-symbol\-source\ <SOURCE>\f[]
.PP
Specifies the symbol server URL.
.PP
\f[C]\-t|\-\-timeout\ <TIMEOUT>\f[]
.PP
Specifies the timeout for pushing to a server in seconds.
Defaults to 300 seconds (5 minutes).
Specifying 0 (zero seconds) applies the default value.
.SS .NET Core 1.x
.PP
\f[C]\-d|\-\-disable\-buffering\f[]
.PP
Disables buffering when pushing to an HTTP(S) server to reduce memory usage.
.PP
\f[C]\-\-force\-english\-output\f[]
.PP
Forces the application to run using an invariant, English\-based culture.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-k|\-\-api\-key\ <API_KEY>\f[]
.PP
The API key for the server.
.PP
\f[C]\-n|\-\-no\-symbols\f[]
.PP
Doesn't push symbols (even if present).
.PP
\f[C]\-s|\-\-source\ <SOURCE>\f[]
.PP
Specifies the server URL.
This option is required unless \f[C]DefaultPushSource\f[] config value is set in the NuGet config file.
.PP
\f[C]\-sk|\-\-symbol\-api\-key\ <API_KEY>\f[]
.PP
The API key for the symbol server.
.PP
\f[C]\-ss|\-\-symbol\-source\ <SOURCE>\f[]
.PP
Specifies the symbol server URL.
.PP
@ -42,32 +174,14 @@ Specifies the timeout for pushing to a server in seconds.
Defaults to 300 seconds (5 minutes).
Specifying 0 (zero seconds) applies the default value.
.PP
\f[C]\-k|\-\-api\-key\ <API_KEY>\f[]
.PP
The API key for the server.
.PP
\f[C]\-\-symbol\-api\-key\ <API_KEY>\f[]
.PP
The API key for the symbol server.
.PP
\f[C]\-d|\-\-disable\-buffering\f[]
.PP
Disables buffering when pushing to an HTTP(S) server to decrease memory usage.
.PP
\f[C]\-n|\-\-no\-symbols\f[]
.PP
Doesn't push symbols (even if present).
.PP
\f[C]\-\-force\-english\-output\f[]
.PP
Forces all logged output in English.
* * * * *
.SH EXAMPLES
.PP
Pushes \f[I]foo.nupkg\f[] to the default push source, providing an API key:
Pushes \f[I]foo.nupkg\f[] to the default push source, specifying an API key:
.PP
\f[C]dotnet\ nuget\ push\ foo.nupkg\ \-k\ 4003d786\-cc37\-4004\-bfdf\-c4f3e8ef9b3a\f[]
.PP
Push \f[I]foo.nupkg\f[] to the custom push source \f[C]http://customsource\f[], providing an API key:
Push \f[I]foo.nupkg\f[] to the custom push source \f[C]http://customsource\f[], specifying an API key:
.PP
\f[C]dotnet\ nuget\ push\ foo.nupkg\ \-k\ 4003d786\-cc37\-4004\-bfdf\-c4f3e8ef9b3a\ \-s\ http://customsource/\f[]
.PP
@ -79,7 +193,7 @@ Pushes \f[I]foo.symbols.nupkg\f[] to the default symbols source:
.PP
\f[C]dotnet\ nuget\ push\ foo.symbols.nupkg\f[]
.PP
Pushes \f[I]foo.nupkg\f[] to the default push source, specifying a 360 second timeout:
Pushes \f[I]foo.nupkg\f[] to the default push source, specifying a 360\-second timeout:
.PP
\f[C]dotnet\ nuget\ push\ foo.nupkg\ \-\-timeout\ 360\f[]
.PP

20
Documentation/manpages/sdk/dotnet-pack.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet pack command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -21,7 +21,8 @@ dotnet\ pack\ [\-h|\-\-help]
.IP
.nf
\f[C]
dotnet\ pack\ [<PROJECT>]\ [\-c|\-\-configuration]\ [\-\-include\-source]\ [\-\-include\-symbols]\ [\-\-no\-build]\ [\-o|\-\-output]\ [\-s|\-\-serviceable]\ [\-v|\-\-verbosity]\ [\-\-version\-suffix]
dotnet\ pack\ [<PROJECT>]\ [\-c|\-\-configuration]\ [\-\-include\-source]\ [\-\-include\-symbols]\ [\-\-no\-build]\ [\-o|\-\-output]
\ \ \ \ [\-s|\-\-serviceable]\ [\-v|\-\-verbosity]\ [\-\-version\-suffix]
dotnet\ pack\ [\-h|\-\-help]
\f[]
.fi
@ -39,7 +40,7 @@ Currently, you must have a package per project if you have project\-to\-project
.PP
By default, \f[C]dotnet\ pack\f[] builds the project first.
If you wish to avoid this behavior, pass the \f[C]\-\-no\-build\f[] option.
This is often useful in Continuous Integration (CI) build scenarios where you know the code was previously built.
This option is often useful in Continuous Integration (CI) build scenarios where you know the code was previously built.
.PP
You can provide MSBuild properties to the \f[C]dotnet\ pack\f[] command for the packing process.
For more information, see NuGet metadata properties and the MSBuild Command\-Line Reference.
@ -51,7 +52,7 @@ The Examples section shows how to use the MSBuild /p switch for a couple of diff
.PP
The project to pack.
It's either a path to a csproj file or to a directory.
If omitted, it defaults to the current directory.
If not specified, it defaults to the current directory.
.SH OPTIONS
.SS .NET Core 2.x
.PP
@ -60,8 +61,10 @@ If omitted, it defaults to the current directory.
Defines the build configuration.
The default value is \f[C]Debug\f[].
.PP
\f[C]\-\-force\f[] 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.
\f[C]\-\-force\f[]
.PP
Forces all dependencies to be resolved even if the last restore was successful.
Specifying this flag is the same as deleting the \f[I]project.assets.json\f[] file.
.PP
\f[C]\-h|\-\-help\f[]
.PP
@ -79,6 +82,7 @@ Generates the symbols \f[C]nupkg\f[].
\f[C]\-\-no\-build\f[]
.PP
Doesn't build the project before packing.
It also implicit sets the \f[C]\-\-no\-restore\f[] flag.
.PP
\f[C]\-\-no\-dependencies\f[]
.PP
@ -86,13 +90,13 @@ Ignores project\-to\-project references and only restores the root project.
.PP
\f[C]\-\-no\-restore\f[]
.PP
Doesn't perform an implicit restore when running the command.
Doesn't execute an implicit restore when running the command.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
Places the built packages in the directory specified.
.PP
\f[C]\-r|\-\-runtime\ <RUNTIME_IDENTIFIER>\f[]
\f[C]\-\-runtime\ <RUNTIME_IDENTIFIER>\f[]
.PP
Specifies the target runtime to restore packages for.
For a list of Runtime Identifiers (RIDs), see the RID catalog.

114
Documentation/manpages/sdk/dotnet-publish.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet publish command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -8,11 +8,21 @@
.PP
\f[C]dotnet\ publish\f[] \- Packs the application and its dependencies into a folder for deployment to a hosting system.
.SH SYNOPSIS
.SS .NET Core 2.x
.SS .NET Core 2.1
.IP
.nf
\f[C]
dotnet\ publish\ [<PROJECT>]\ [\-c|\-\-configuration]\ [\-f|\-\-framework]\ [\-\-force]\ [\-\-manifest]\ [\-\-no\-dependencies]\ [\-\-no\-restore]\ [\-o|\-\-output]\ [\-r|\-\-runtime]\ [\-\-self\-contained]\ [\-v|\-\-verbosity]\ [\-\-version\-suffix]
dotnet\ publish\ [<PROJECT>]\ [\-c|\-\-configuration]\ [\-f|\-\-framework]\ [\-\-force]\ [\-\-manifest]\ [\-\-no\-build]\ [\-\-no\-dependencies]
\ \ \ \ [\-\-no\-restore]\ [\-o|\-\-output]\ [\-r|\-\-runtime]\ [\-\-self\-contained]\ [\-v|\-\-verbosity]\ [\-\-version\-suffix]
dotnet\ publish\ [\-h|\-\-help]
\f[]
.fi
.SS .NET Core 2.0
.IP
.nf
\f[C]
dotnet\ publish\ [<PROJECT>]\ [\-c|\-\-configuration]\ [\-f|\-\-framework]\ [\-\-force]\ [\-\-manifest]\ [\-\-no\-dependencies]
\ \ \ \ [\-\-no\-restore]\ [\-o|\-\-output]\ [\-r|\-\-runtime]\ [\-\-self\-contained]\ [\-v|\-\-verbosity]\ [\-\-version\-suffix]
dotnet\ publish\ [\-h|\-\-help]
\f[]
.fi
@ -20,7 +30,8 @@ dotnet\ publish\ [\-h|\-\-help]
.IP
.nf
\f[C]
dotnet\ publish\ [<PROJECT>]\ [\-c|\-\-configuration]\ [\-f|\-\-framework]\ [\-o|\-\-output]\ [\-r|\-\-runtime]\ [\-v|\-\-verbosity]\ [\-\-version\-suffix]
dotnet\ publish\ [<PROJECT>]\ [\-c|\-\-configuration]\ [\-f|\-\-framework]\ [\-o|\-\-output]\ [\-r|\-\-runtime]\ [\-v|\-\-verbosity]
\ \ \ \ [\-\-version\-suffix]
dotnet\ publish\ [\-h|\-\-help]
\f[]
.fi
@ -29,18 +40,18 @@ dotnet\ publish\ [\-h|\-\-help]
.SH DESCRIPTION
.PP
\f[C]dotnet\ publish\f[] compiles the application, reads through its dependencies specified in the project file, and publishes the resulting set of files to a directory.
The output will contain the following:
The output includes the following assets:
.IP \[bu] 2
Intermediate Language (IL) code in an assembly with a \f[I]dll\f[] extension.
.IP \[bu] 2
\f[I].deps.json\f[] file that contains all of the dependencies of the project.
\f[I].deps.json\f[] file that includes all of the dependencies of the project.
.IP \[bu] 2
\f[I].runtime.config.json\f[] file that specifies the shared runtime that the application expects, as well as other configuration options for the runtime (for example, garbage collection type).
.IP \[bu] 2
The application's dependencies.
These are copied from the NuGet cache into the output folder.
The application's dependencies, which are copied from the NuGet cache into the output folder.
.PP
The \f[C]dotnet\ publish\f[] command's output is ready for deployment to a hosting system (for example, a server, PC, Mac, laptop) for execution and is the only officially supported way to prepare the application for deployment.
The \f[C]dotnet\ publish\f[] command's output is ready for deployment to a hosting system (for example, a server, PC, Mac, laptop) for execution.
It's the only officially supported way to prepare the application for deployment.
Depending on the type of deployment that the project specifies, the hosting system may or may not have the .NET Core shared runtime installed on it.
For more information, see .NET Core Application Deployment.
For the directory structure of a published application, see Directory structure.
@ -49,9 +60,10 @@ For the directory structure of a published application, see Directory structure.
.PP
\f[C]PROJECT\f[]
.PP
The project to publish, which defaults to the current directory if not specified.
The project to publish.
If not specified, it defaults to the current directory.
.SH OPTIONS
.SS .NET Core 2.x
.SS .NET Core 2.1
.PP
\f[C]\-c|\-\-configuration\ {Debug|Release}\f[]
.PP
@ -66,7 +78,75 @@ You must specify the target framework 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
Prints out a short help for the command.
.PP
\f[C]\-\-manifest\ <PATH_TO_MANIFEST_FILE>\f[]
.PP
Specifies one or several target manifests to use to trim the set of packages published with the app.
The manifest file is part of the output of the \f[C]dotnet\ store\f[].
To specify multiple manifests, add a \f[C]\-\-manifest\f[] option for each manifest.
This option is available starting with .NET Core 2.0 SDK.
.PP
\f[C]\-\-no\-build\f[]
.PP
Doesn't build the project before publishing.
It also implicit sets the \f[C]\-\-no\-restore\f[] flag.
.PP
\f[C]\-\-no\-dependencies\f[]
.PP
Ignores project\-to\-project references and only restores the root project.
.PP
\f[C]\-\-no\-restore\f[]
.PP
Doesn't execute an implicit restore when running the command.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
Specifies the path for the output directory.
If not specified, it defaults to \f[I]./bin/[configuration]/[framework]/publish/\f[] for a framework\-dependent deployment or \f[I]./bin/[configuration]/[framework]/[runtime]/publish/\f[] for a self\-contained deployment.
If the path is relative, the output directory generated is relative to the project file location, not to the current working directory.
.PP
\f[C]\-\-self\-contained\f[]
.PP
Publishes the .NET Core runtime with your application so the runtime doesn't need to be installed on the target machine.
If a runtime identifier is specified, its default value is \f[C]true\f[].
For more information about the different deployment types, see .NET Core application deployment.
.PP
\f[C]\-r|\-\-runtime\ <RUNTIME_IDENTIFIER>\f[]
.PP
Publishes the application for a given runtime.
This is used when creating a self\-contained deployment (SCD).
For a list of Runtime Identifiers (RIDs), see the RID catalog.
Default is to publish a framework\-dependent deployment (FDD).
.PP
\f[C]\-v|\-\-verbosity\ <LEVEL>\f[]
.PP
Sets the verbosity level of the command.
Allowed values are \f[C]q[uiet]\f[], \f[C]m[inimal]\f[], \f[C]n[ormal]\f[], \f[C]d[etailed]\f[], and \f[C]diag[nostic]\f[].
.PP
\f[C]\-\-version\-suffix\ <VERSION_SUFFIX>\f[]
.PP
Defines the version suffix to replace the asterisk (\f[C]*\f[]) in the version field of the project file.
.SS .NET Core 2.0
.PP
\f[C]\-c|\-\-configuration\ {Debug|Release}\f[]
.PP
Defines the build configuration.
The default value is \f[C]Debug\f[].
.PP
\f[C]\-f|\-\-framework\ <FRAMEWORK>\f[]
.PP
Publishes the application for the specified target framework.
You must specify the target framework in the project file.
.PP
\f[C]\-\-force\f[]
.PP
Forces all dependencies to be resolved even if the last restore was successful.
Specifying this flag is the same as deleting the \f[I]project.assets.json\f[] file.
.PP
\f[C]\-h|\-\-help\f[]
.PP
@ -85,13 +165,13 @@ Ignores project\-to\-project references and only restores the root project.
.PP
\f[C]\-\-no\-restore\f[]
.PP
Doesn't perform an implicit restore when running the command.
Doesn't execute an implicit restore when running the command.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
Specifies the path for the output directory.
If not specified, it defaults to \f[I]./bin/[configuration]/[framework]/\f[] for a framework\-dependent deployment or \f[I]./bin/[configuration]/[framework]/[runtime]\f[] for a self\-contained deployment.
If a relative path is provided, the output directory generated is relative to the project file location, not to the current working directory.
If not specified, it defaults to \f[I]./bin/[configuration]/[framework]/publish/\f[] for a framework\-dependent deployment or \f[I]./bin/[configuration]/[framework]/[runtime]/publish/\f[] for a self\-contained deployment.
If the path is relative, the output directory generated is relative to the project file location, not to the current working directory.
.PP
\f[C]\-\-self\-contained\f[]
.PP
@ -140,8 +220,8 @@ This option is available starting with .NET Core 2.0 SDK.
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
Specifies the path for the output directory.
If not specified, it defaults to \f[I]./bin/[configuration]/[framework]/\f[] for a framework\-dependent deployment or \f[I]./bin/[configuration]/[framework]/[runtime]\f[] for a self\-contained deployment.
If a relative path is provided, the output directory generated is relative to the project file location, not to the current working directory.
If not specified, it defaults to \f[I]./bin/[configuration]/[framework]/publish/\f[] for a framework\-dependent deployment or \f[I]./bin/[configuration]/[framework]/[runtime]/publish/\f[] for a self\-contained deployment.
If the path is relative, the output directory generated is relative to the project file location, not to the current working directory.
.PP
\f[C]\-r|\-\-runtime\ <RUNTIME_IDENTIFIER>\f[]
.PP

4
Documentation/manpages/sdk/dotnet-remove-package.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet remove package command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -18,7 +18,7 @@ The \f[C]dotnet\ remove\ package\f[] command provides a convenient option to rem
\f[C]PROJECT\f[]
.PP
Specifies the project file.
If not specified, the command will search the current directory for one.
If not specified, the command searches the current directory for one.
.PP
\f[C]PACKAGE_NAME\f[]
.PP

4
Documentation/manpages/sdk/dotnet-remove-reference.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet remove reference command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -22,7 +22,7 @@ If not specified, the command searches the current directory for one.
.PP
\f[C]PROJECT_REFERENCES\f[]
.PP
Project to project (P2P references to remove.
Project\-to\-project (P2P) references to remove.
You can specify one or multiple projects.
Glob patterns are supported on Unix/Linux based terminals.
.SH OPTIONS

25
Documentation/manpages/sdk/dotnet-restore.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet restore command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -12,7 +12,8 @@
.IP
.nf
\f[C]
dotnet\ restore\ [<ROOT>]\ [\-\-configfile]\ [\-\-disable\-parallel]\ [\-\-force]\ [\-\-ignore\-failed\-sources]\ [\-\-no\-cache]\ [\-\-no\-dependencies]\ [\-\-packages]\ [\-r|\-\-runtime]\ [\-s|\-\-source]\ [\-v|\-\-verbosity]
dotnet\ restore\ [<ROOT>]\ [\-\-configfile]\ [\-\-disable\-parallel]\ [\-\-force]\ [\-\-ignore\-failed\-sources]\ [\-\-no\-cache]
\ \ \ \ [\-\-no\-dependencies]\ [\-\-packages]\ [\-r|\-\-runtime]\ [\-s|\-\-source]\ [\-v|\-\-verbosity]
dotnet\ restore\ [\-h|\-\-help]
\f[]
.fi
@ -20,7 +21,8 @@ dotnet\ restore\ [\-h|\-\-help]
.IP
.nf
\f[C]
dotnet\ restore\ [<ROOT>]\ [\-\-configfile]\ [\-\-disable\-parallel]\ [\-\-ignore\-failed\-sources]\ [\-\-no\-cache]\ [\-\-no\-dependencies]\ [\-\-packages]\ [\-r|\-\-runtime]\ [\-s|\-\-source]\ [\-v|\-\-verbosity]
dotnet\ restore\ [<ROOT>]\ [\-\-configfile]\ [\-\-disable\-parallel]\ [\-\-ignore\-failed\-sources]\ [\-\-no\-cache]
\ \ \ \ [\-\-no\-dependencies]\ [\-\-packages]\ [\-r|\-\-runtime]\ [\-s|\-\-source]\ [\-v|\-\-verbosity]
dotnet\ restore\ [\-h|\-\-help]
\f[]
.fi
@ -29,17 +31,18 @@ dotnet\ restore\ [\-h|\-\-help]
.SH DESCRIPTION
.PP
The \f[C]dotnet\ restore\f[] command uses NuGet to restore dependencies as well as project\-specific tools that are specified in the project file.
By default, the restoration of dependencies and tools are performed in parallel.
By default, the restoration of dependencies and tools are executed in parallel.
.PP
.PP
In order to restore the dependencies, NuGet needs the feeds where the packages are located.
To restore the dependencies, NuGet needs the feeds where the packages are located.
Feeds are usually provided via the \f[I]NuGet.config\f[] configuration file.
A default configuration file is provided when the CLI tools are installed.
You specify additional feeds by creating your own \f[I]NuGet.config\f[] file in the project directory.
You also specify additional feeds per invocation at a command prompt.
.PP
For dependencies, you specify where the restored packages are placed during the restore operation using the \f[C]\-\-packages\f[] argument.
If not specified, the default NuGet package cache is used, which is found in the \f[C]\&.nuget/packages\f[] directory in the user's home directory on all operating systems (for example, \f[I]/home/user1\f[] on Linux or \f[I]C:1\f[] on Windows).
If not specified, the default NuGet package cache is used, which is found in the \f[C]\&.nuget/packages\f[] directory in the user's home directory on all operating systems.
For example, \f[I]/home/user1\f[] on Linux or \f[I]C:1\f[] on Windows.
.PP
For project\-specific tooling, \f[C]dotnet\ restore\f[] first restores the package in which the tool is packed, and then proceeds to restore the tool's dependencies as specified in its project file.
.PP
@ -55,6 +58,8 @@ Starting with .NET Core 2.0, \f[C]dotnet\ restore\f[] is run implicitly if neces
.IP \[bu] 2
\f[C]dotnet\ build\f[]
.IP \[bu] 2
\f[C]dotnet\ build\ server\f[]
.IP \[bu] 2
\f[C]dotnet\ run\f[]
.IP \[bu] 2
\f[C]dotnet\ test\f[]
@ -65,9 +70,9 @@ Starting with .NET Core 2.0, \f[C]dotnet\ restore\f[] is run implicitly if neces
.PP
In most cases, you no longer need to explicitly use the \f[C]dotnet\ restore\f[] command.
.PP
In some cases, it is inconvenient for \f[C]dotnet\ restore\f[] to run implicitly.
Sometimes, it might be inconvenient to run \f[C]dotnet\ restore\f[] implicitly.
For example, some automated systems, such as build systems, need to call \f[C]dotnet\ restore\f[] explicitly to control when the restore occurs so that they can control network usage.
To prevent \f[C]dotnet\ restore\f[] from running implicitly, you can use the \f[C]\-\-no\-restore\f[] switch with any of these commands to disable implicit restore.
To prevent \f[C]dotnet\ restore\f[] from running implicitly, you can use the \f[C]\-\-no\-restore\f[] flag with any of these commands to disable implicit restore.
.SS Arguments
.PP
\f[C]ROOT\f[]
@ -87,7 +92,7 @@ Disables restoring multiple projects in parallel.
\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
@ -119,7 +124,7 @@ Provide multiple RIDs by specifying this option multiple times.
\f[C]\-s|\-\-source\ <SOURCE>\f[]
.PP
Specifies a NuGet package source to use during the restore operation.
This overrides all of the sources specified in the \f[I]NuGet.config\f[] files.
This setting overrides all of the sources specified in the \f[I]NuGet.config\f[] files.
Multiple sources can be provided by specifying this option multiple times.
.PP
\f[C]\-\-verbosity\ <LEVEL>\f[]

100
Documentation/manpages/sdk/dotnet-run.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet run command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -8,11 +8,21 @@
.PP
\f[C]dotnet\ run\f[] \- Runs source code without any explicit compile or launch commands.
.SH SYNOPSIS
.SS .NET Core 2.x
.SS .NET Core 2.1
.IP
.nf
\f[C]
dotnet\ run\ [\-c|\-\-configuration]\ [\-f|\-\-framework]\ [\-\-force]\ [\-\-launch\-profile]\ [\-\-no\-build]\ [\-\-no\-dependencies]\ [\-\-no\-launch\-profile]\ [\-\-no\-restore]\ [\-p|\-\-project]\ [\-\-runtime]\ [[\-\-]\ [application\ arguments]]
dotnet\ run\ [\-c|\-\-configuration]\ [\-f|\-\-framework]\ [\-\-force]\ [\-\-launch\-profile]\ [\-\-no\-build]\ [\-\-no\-dependencies]
\ \ \ \ [\-\-no\-launch\-profile]\ [\-\-no\-restore]\ [\-p|\-\-project]\ [\-\-runtime]\ [\-v|\-\-verbosity]\ [[\-\-]\ [application\ arguments]]
dotnet\ run\ [\-h|\-\-help]
\f[]
.fi
.SS .NET Core 2.0
.IP
.nf
\f[C]
dotnet\ run\ [\-c|\-\-configuration]\ [\-f|\-\-framework]\ [\-\-force]\ [\-\-launch\-profile]\ [\-\-no\-build]\ [\-\-no\-dependencies]
\ \ \ \ [\-\-no\-launch\-profile]\ [\-\-no\-restore]\ [\-p|\-\-project]\ [\-\-runtime]\ [[\-\-]\ [application\ arguments]]
dotnet\ run\ [\-h|\-\-help]
\f[]
.fi
@ -52,17 +62,17 @@ dotnet\ myapp.dll
.PP
For more information on the \f[C]dotnet\f[] driver, see the .NET Core Command Line Tools (CLI) topic.
.PP
In order to run the application, the \f[C]dotnet\ run\f[] command resolves the dependencies of the application that are outside of the shared runtime from the NuGet cache.
To run the application, the \f[C]dotnet\ run\f[] command resolves the dependencies of the application that are outside of the shared runtime from the NuGet cache.
Because it uses cached dependencies, it's not recommended to use \f[C]dotnet\ run\f[] to run applications in production.
Instead, create a deployment using the \f[C]dotnet\ publish\f[] command and deploy the published output.
.PP
.SH OPTIONS
.SS .NET Core 2.x
.SS .NET Core 2.1
.PP
\f[C]\-\-\f[]
.PP
Delimits arguments to \f[C]dotnet\ run\f[] from arguments for the application being run.
All arguments after this one are passed to the application run.
All arguments after this delimiter are passed to the application run.
.PP
\f[C]\-c|\-\-configuration\ {Debug|Release}\f[]
.PP
@ -77,7 +87,7 @@ The framework must be specified 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 \f[I]project.assets.json\f[].
Specifying this flag is the same as deleting the \f[I]project.assets.json\f[] file.
.PP
\f[C]\-h|\-\-help\f[]
.PP
@ -86,12 +96,13 @@ Prints out a short help for the command.
\f[C]\-\-launch\-profile\ <NAME>\f[]
.PP
The name of the launch profile (if any) to use when launching the application.
Launch profiles are defined in the \f[I]launchSettings.json\f[] file and are typically called \f[C]Development\f[], \f[C]Staging\f[] and \f[C]Production\f[].
Launch profiles are defined in the \f[I]launchSettings.json\f[] file and are typically called \f[C]Development\f[], \f[C]Staging\f[], and \f[C]Production\f[].
For more information, see Working with multiple environments.
.PP
\f[C]\-\-no\-build\f[]
.PP
Doesn't build the project before running.
It also implicit sets the \f[C]\-\-no\-restore\f[] flag.
.PP
\f[C]\-\-no\-dependencies\f[]
.PP
@ -99,16 +110,79 @@ When restoring a project with project\-to\-project (P2P) references, restores th
.PP
\f[C]\-\-no\-launch\-profile\f[]
.PP
Doesn't attempt to use \f[I]launchSettings.json\f[] to configure the application.
Doesn't try to use \f[I]launchSettings.json\f[] to configure the application.
.PP
\f[C]\-\-no\-restore\f[]
.PP
Doesn't perform an implicit restore when running the command.
Doesn't execute an implicit restore when running the command.
.PP
\f[C]\-p|\-\-project\ <PATH>\f[]
.PP
Specifies the path of the project file to run (folder name or full path).
It defaults to the current directory if not specified.
If not specified, it defaults to the current directory.
.PP
\f[C]\-\-runtime\ <RUNTIME_IDENTIFIER>\f[]
.PP
Specifies the target runtime to restore packages for.
For a list of Runtime Identifiers (RIDs), see the RID catalog.
.PP
\f[C]\-v|\-\-verbosity\ <LEVEL>\f[]
.PP
Sets the verbosity level of the command.
Allowed values are \f[C]q[uiet]\f[], \f[C]m[inimal]\f[], \f[C]n[ormal]\f[], \f[C]d[etailed]\f[], and \f[C]diag[nostic]\f[].
.SS .NET Core 2.0
.PP
\f[C]\-\-\f[]
.PP
Delimits arguments to \f[C]dotnet\ run\f[] from arguments for the application being run.
All arguments after this delimiter are passed to the application run.
.PP
\f[C]\-c|\-\-configuration\ {Debug|Release}\f[]
.PP
Defines the build configuration.
The default value is \f[C]Debug\f[].
.PP
\f[C]\-f|\-\-framework\ <FRAMEWORK>\f[]
.PP
Builds and runs the app using the specified framework.
The framework must be specified in the project file.
.PP
\f[C]\-\-force\f[]
.PP
Forces all dependencies to be resolved even if the last restore was successful.
Specifying this flag is the same as deleting the \f[I]project.assets.json\f[] file.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-\-launch\-profile\ <NAME>\f[]
.PP
The name of the launch profile (if any) to use when launching the application.
Launch profiles are defined in the \f[I]launchSettings.json\f[] file and are typically called \f[C]Development\f[], \f[C]Staging\f[], and \f[C]Production\f[].
For more information, see Working with multiple environments.
.PP
\f[C]\-\-no\-build\f[]
.PP
Doesn't build the project before running.
It also implicit sets the \f[C]\-\-no\-restore\f[] flag.
.PP
\f[C]\-\-no\-dependencies\f[]
.PP
When restoring a project with project\-to\-project (P2P) references, restores the root project and not the references.
.PP
\f[C]\-\-no\-launch\-profile\f[]
.PP
Doesn't try to use \f[I]launchSettings.json\f[] to configure the application.
.PP
\f[C]\-\-no\-restore\f[]
.PP
Doesn't execute an implicit restore when running the command.
.PP
\f[C]\-p|\-\-project\ <PATH>\f[]
.PP
Specifies the path of the project file to run (folder name or full path).
If not specified, it defaults to the current directory.
.PP
\f[C]\-\-runtime\ <RUNTIME_IDENTIFIER>\f[]
.PP
@ -119,7 +193,7 @@ For a list of Runtime Identifiers (RIDs), see the RID catalog.
\f[C]\-\-\f[]
.PP
Delimits arguments to \f[C]dotnet\ run\f[] from arguments for the application being run.
All arguments after this one are passed to the application run.
All arguments after this delimiter are passed to the application run.
.PP
\f[C]\-c|\-\-configuration\ {Debug|Release}\f[]
.PP
@ -138,7 +212,7 @@ Prints out a short help for the command.
\f[C]\-p|\-\-project\ <PATH/PROJECT.csproj>\f[]
.PP
Specifies the path and name of the project file.
(See the NOTE.) It defaults to the current directory if not specified.
(See the NOTE.) If not specified, it defaults to the current directory.
.RS
.PP
[!NOTE] Use the path and name of the project file with the \f[C]\-p|\-\-project\f[] option.

2
Documentation/manpages/sdk/dotnet-sln.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet sln command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy

9
Documentation/manpages/sdk/dotnet-store.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet store command" "1" "" "" ".NET Core"
.hy
@ -24,9 +24,10 @@ Specifies the target framework.
\f[C]\-m|\-\-manifest\ <PATH_TO_MANIFEST_FILE>\f[]
.PP
The \f[I]package store manifest file\f[] is an XML file that contains the list of packages to store.
The format of the manifest file is compatible with the \f[I]csproj\f[] format.
So, a \f[I]csproj\f[] project file that references the desired packages can be used with the \f[C]\-m|\-\-manifest\f[] option to store assemblies in the runtime package store.
To specify multiple manifest files, repeat the option and path for each file: \f[C]\-\-manifest\ packages1.csproj\ \-\-manifest\ packages2.csproj\f[].
The format of the manifest file is compatible with the SDK\-style project format.
So, a project file that references the desired packages can be used with the \f[C]\-m|\-\-manifest\f[] option to store assemblies in the runtime package store.
To specify multiple manifest files, repeat the option and path for each file.
For example: \f[C]\-\-manifest\ packages1.csproj\ \-\-manifest\ packages2.csproj\f[].
.PP
\f[C]\-r|\-\-runtime\ <RUNTIME_IDENTIFIER>\f[]
.PP

119
Documentation/manpages/sdk/dotnet-test.1
View file

@ -1,5 +1,5 @@
.\"t
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet test command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -9,11 +9,21 @@
.PP
\f[C]dotnet\ test\f[] \- .NET test driver used to execute unit tests.
.SH SYNOPSIS
.SS .NET Core 2.x
.SS .NET Core 2.1
.IP
.nf
\f[C]
dotnet\ test\ [<PROJECT>]\ [\-a|\-\-test\-adapter\-path]\ [\-c|\-\-configuration]\ [\-\-collect]\ [\-d|\-\-diag]\ [\-f|\-\-framework]\ [\-\-filter]\ [\-l|\-\-logger]\ [\-\-no\-build]\ [\-\-no\-restore]\ [\-o|\-\-output]\ [\-r|\-\-results\-directory]\ [\-s|\-\-settings]\ [\-t|\-\-list\-tests]\ [\-v|\-\-verbosity]
dotnet\ test\ [<PROJECT>]\ [\-a|\-\-test\-adapter\-path]\ [\-\-blame]\ [\-c|\-\-configuration]\ [\-\-collect]\ [\-d|\-\-diag]\ [\-f|\-\-framework]\ [\-\-filter]
\ \ \ \ [\-l|\-\-logger]\ [\-\-no\-build]\ [\-\-no\-restore]\ [\-o|\-\-output]\ [\-r|\-\-results\-directory]\ [\-s|\-\-settings]\ [\-t|\-\-list\-tests]\ [\-v|\-\-verbosity]
dotnet\ test\ [\-h|\-\-help]
\f[]
.fi
.SS .NET Core 2.0
.IP
.nf
\f[C]
dotnet\ test\ [<PROJECT>]\ [\-a|\-\-test\-adapter\-path]\ [\-c|\-\-configuration]\ [\-\-collect]\ [\-d|\-\-diag]\ [\-f|\-\-framework]\ [\-\-filter]
\ \ \ \ [\-l|\-\-logger]\ [\-\-no\-build]\ [\-\-no\-restore]\ [\-o|\-\-output]\ [\-r|\-\-results\-directory]\ [\-s|\-\-settings]\ [\-t|\-\-list\-tests]\ [\-v|\-\-verbosity]
dotnet\ test\ [\-h|\-\-help]
\f[]
.fi
@ -41,10 +51,84 @@ Test projects specify the test runner using an ordinary \f[C]<PackageReference>\
.PP
\f[C]PROJECT\f[]
.PP
Specifies a path to the test project.
If omitted, it defaults to current directory.
Path to the test project.
If not specified, it defaults to current directory.
.SH OPTIONS
.SS .NET Core 2.x
.SS .NET Core 2.1
.PP
\f[C]\-a|\-\-test\-adapter\-path\ <PATH_TO_ADAPTER>\f[]
.PP
Use the custom test adapters from the specified path in the test run.
.PP
\f[C]\-\-blame\f[]
.PP
Runs the tests in blame mode.
This option is helpful in isolating the problematic tests causing test host to crash.
It creates an output file in the current directory as \f[I]Sequence.xml\f[] that captures the order of tests execution before the crash.
.PP
\f[C]\-c|\-\-configuration\ {Debug|Release}\f[]
.PP
Defines the build configuration.
The default value is \f[C]Debug\f[], but your project's configuration could override this default SDK setting.
.PP
\f[C]\-\-collect\ <DATA_COLLECTOR_FRIENDLY_NAME>\f[]
.PP
Enables data collector for the test run.
For more information, see Monitor and analyze test run.
.PP
\f[C]\-d|\-\-diag\ <PATH_TO_DIAGNOSTICS_FILE>\f[]
.PP
Enables diagnostic mode for the test platform and write diagnostic messages to the specified file.
.PP
\f[C]\-f|\-\-framework\ <FRAMEWORK>\f[]
.PP
Looks for test binaries for a specific framework.
.PP
\f[C]\-\-filter\ <EXPRESSION>\f[]
.PP
Filters out tests in the current project using the given expression.
For more information, see the Filter option details section.
For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-l|\-\-logger\ <LoggerUri/FriendlyName>\f[]
.PP
Specifies a logger for test results.
.PP
\f[C]\-\-no\-build\f[]
.PP
Doesn't build the test project before running it.
It also implicit sets the \f[C]\-\-no\-restore\f[] flag.
.PP
\f[C]\-\-no\-restore\f[]
.PP
Doesn't execute an implicit restore when running the command.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
Directory in which to find the binaries to run.
.PP
\f[C]\-r|\-\-results\-directory\ <PATH>\f[]
.PP
The directory where the test results are going to be placed.
If the specified directory doesn't exist, it's created.
.PP
\f[C]\-s|\-\-settings\ <SETTINGS_FILE>\f[]
.PP
Settings to use when running tests.
.PP
\f[C]\-t|\-\-list\-tests\f[]
.PP
List all of the discovered tests in the current project.
.PP
\f[C]\-v|\-\-verbosity\ <LEVEL>\f[]
.PP
Sets the verbosity level of the command.
Allowed values are \f[C]q[uiet]\f[], \f[C]m[inimal]\f[], \f[C]n[ormal]\f[], \f[C]d[etailed]\f[], and \f[C]diag[nostic]\f[].
.SS .NET Core 2.0
.PP
\f[C]\-a|\-\-test\-adapter\-path\ <PATH_TO_ADAPTER>\f[]
.PP
@ -72,7 +156,7 @@ Looks for test binaries for a specific framework.
.PP
Filters out tests in the current project using the given expression.
For more information, see the Filter option details section.
For additional information and examples on how to use selective unit test filtering, see Running selective unit tests.
For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
.PP
\f[C]\-h|\-\-help\f[]
.PP
@ -84,11 +168,12 @@ Specifies a logger for test results.
.PP
\f[C]\-\-no\-build\f[]
.PP
Does not build the test project prior to running it.
Doesn't build the test project before running it.
It also implicit sets the \f[C]\-\-no\-restore\f[] flag.
.PP
\f[C]\-\-no\-restore\f[]
.PP
Doesn't perform an implicit restore when running the command.
Doesn't execute an implicit restore when running the command.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
@ -97,7 +182,7 @@ Directory in which to find the binaries to run.
\f[C]\-r|\-\-results\-directory\ <PATH>\f[]
.PP
The directory where the test results are going to be placed.
The specified directory will be created if it doesn't exist.
If the specified directory doesn't exist, it's created.
.PP
\f[C]\-s|\-\-settings\ <SETTINGS_FILE>\f[]
.PP
@ -134,7 +219,7 @@ Looks for test binaries for a specific framework.
.PP
Filters out tests in the current project using the given expression.
For more information, see the Filter option details section.
For additional information and examples on how to use selective unit test filtering, see Running selective unit tests.
For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
.PP
\f[C]\-h|\-\-help\f[]
.PP
@ -146,7 +231,7 @@ Specifies a logger for test results.
.PP
\f[C]\-\-no\-build\f[]
.PP
Does not build the test project prior to running it.
Doesn't build the test project before running it.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
@ -186,7 +271,7 @@ The following are the properties supported by popular unit test frameworks:
.PP
.TS
tab(@);
c l.
l l.
T{
Test Framework
T}@T{
@ -200,7 +285,7 @@ Name
ClassName
Priority
TestCategory
| | Xunit |
| | xUnit |
FullyQualifiedName
DisplayName
Traits
@ -248,7 +333,7 @@ Expressions can be joined with conditional operators:
.PP
.TS
tab(@);
c c.
l l.
T{
Operator
T}@T{
@ -256,7 +341,7 @@ Function
T}
_
T{
| \ \
|
T}@T{
OR \ \ \
T}
@ -269,7 +354,7 @@ T}
.PP
You can enclose expressions in parenthesis when using conditional operators (for example, \f[C](Name~TestMethod1)\ |\ (Name~TestMethod2)\f[]).
.PP
For additional information and examples on how to use selective unit test filtering, see Running selective unit tests.
For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
.SS See also
.PP
Frameworks and Targets

116
Documentation/manpages/sdk/dotnet-tool-install.1 Normal file
View file

@ -0,0 +1,116 @@
.\"t
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet tool install command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
.SH dotnet tool install
.PP
.SH NAME
.PP
\f[C]dotnet\ tool\ install\f[] \- Installs the specified .NET Core Global Tool on your machine.
.SH SYNOPSIS
.IP
.nf
\f[C]
dotnet\ tool\ install\ <PACKAGE_NAME>\ <\-g|\-\-global>\ [\-\-add\-source]\ [\-\-configfile]\ [\-\-framework]\ [\-v|\-\-verbosity]\ [\-\-version]
dotnet\ tool\ install\ <PACKAGE_NAME>\ <\-\-tool\-path>\ [\-\-add\-source]\ [\-\-configfile]\ [\-\-framework]\ [\-v|\-\-verbosity]\ [\-\-version]
dotnet\ tool\ install\ <\-h|\-\-help>
\f[]
.fi
.SH DESCRIPTION
.PP
The \f[C]dotnet\ tool\ install\f[] command provides a way for you to install .NET Core Global Tools on your machine.
To use the command, you either have to specify that you want a user\-wide installation using the \f[C]\-\-global\f[] option or you specify a path to install it using the \f[C]\-\-tool\-path\f[] option.
.PP
Global Tools are installed in the following directories by default when you specify the \f[C]\-g\f[] (or \f[C]\-\-global\f[]) option:
.PP
.TS
tab(@);
l l.
T{
OS
T}@T{
Path
T}
_
T{
Linux/macOS
T}@T{
\f[C]$HOME/.dotnet/tools\f[]
T}
T{
Windows
T}@T{
\f[C]%USERPROFILE%\\.dotnet\\tools\f[]
T}
.TE
.SS Arguments
.PP
\f[C]PACKAGE_NAME\f[]
.PP
Name/ID of the NuGet package that contains the .NET Core Global Tool to install.
.SH OPTIONS
.PP
\f[C]\-\-add\-source\ <SOURCE>\f[]
.PP
Adds an additional NuGet package source to use during installation.
.PP
\f[C]\-\-configfile\ <FILE>\f[]
.PP
The NuGet configuration (\f[I]nuget.config\f[]) file to use.
.PP
\f[C]\-\-framework\ <FRAMEWORK>\f[]
.PP
Specifies the target framework to install the tool for.
By default, the .NET Core SDK tries to choose the most appropriate target framework.
.PP
\f[C]\-g|\-\-global\f[]
.PP
Specifies that the installation is user wide.
Can't be combined with the \f[C]\-\-tool\-path\f[] option.
If you don't specify this option, you must specify the \f[C]\-\-tool\-path\f[] option.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-\-tool\-path\ <PATH>\f[]
.PP
Specifies the location where to install the Global Tool.
PATH can be absolute or relative.
If PATH doesn't exist, the command tries to create it.
Can't be combined with the \f[C]\-\-global\f[] option.
If you don't specify this option, you must specify the \f[C]\-\-global\f[] option.
.PP
\f[C]\-v|\-\-verbosity\ <LEVEL>\f[]
.PP
Sets the verbosity level of the command.
Allowed values are \f[C]q[uiet]\f[], \f[C]m[inimal]\f[], \f[C]n[ormal]\f[], \f[C]d[etailed]\f[], and \f[C]diag[nostic]\f[].
.PP
\f[C]\-\-version\ <VERSION_NUMBER>\f[]
.PP
The version of the tool to install.
By default, the latest stable package version is installed.
Use this option to install preview or older versions of the tool.
.SH EXAMPLES
.PP
Installs the dotnetsay Global Tool in the default location:
.PP
\f[C]dotnet\ tool\ install\ \-g\ dotnetsay\f[]
.PP
Installs the dotnetsay Global Tool on a specific Windows folder:
.PP
\f[C]dotnet\ tool\ install\ dotnetsay\ \-\-tool\-path\ c:\\global\-tools\f[]
.PP
Installs the dotnetsay Global Tool on a specific Linux/macOS folder:
.PP
\f[C]dotnet\ tool\ install\ dotnetsay\ \-\-tool\-path\ ~/bin\f[]
.PP
Installs version 2.0.0 of the dotnetsay Global Tool:
.PP
\f[C]dotnet\ tool\ install\ \-g\ dotnetsay\ \-\-version\ 2.0.0\f[]
.SS See also
.PP
\&.NET Core Global Tools
.SH AUTHORS
mairaw.

59
Documentation/manpages/sdk/dotnet-tool-list.1 Normal file
View file

@ -0,0 +1,59 @@
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet tool list command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
.SH dotnet tool list
.PP
.SH NAME
.PP
\f[C]dotnet\ tool\ list\f[] \- Lists all .NET Core Global Tools currently installed in the default directory on your machine or in the specified path.
.SH SYNOPSIS
.IP
.nf
\f[C]
dotnet\ tool\ list\ <\-g|\-\-global>
dotnet\ tool\ list\ <\-\-tool\-path>
dotnet\ tool\ list\ <\-h|\-\-help>
\f[]
.fi
.SH DESCRIPTION
.PP
The \f[C]dotnet\ tool\ list\f[] command provides a way for you to list all .NET Core Global Tools installed user\-wide on your machine (current user profile) or in the specified path.
The command lists the package name, version installed, and the Global Tool command.
To use the list command, you either have to specify that you want to see all user\-wide tools using the \f[C]\-\-global\f[] option or specify a custom path using the \f[C]\-\-tool\-path\f[] option.
.SH OPTIONS
.PP
\f[C]\-g|\-\-global\f[]
.PP
Lists user\-wide Global Tools.
Can't be combined with the \f[C]\-\-tool\-path\f[] option.
If you don't specify this option, you must specify the \f[C]\-\-tool\-path\f[] option.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-\-tool\-path\ <PATH>\f[]
.PP
Specifies a custom location where to find Global Tools.
PATH can be absolute or relative.
Can't be combined with the \f[C]\-\-global\f[] option.
If you don't specify this option, you must specify the \f[C]\-\-global\f[] option.
.SH EXAMPLES
.PP
Lists all Global Tools installed user\-wide on your machine (current user profile):
.PP
\f[C]dotnet\ tool\ list\ \-g\f[]
.PP
Lists the Global Tools from a specific Windows folder:
.PP
\f[C]dotnet\ tool\ list\ \-\-tool\-path\ c:\\global\-tools\f[]
.PP
Lists the Global Tools from a specific Linux/macOS folder:
.PP
\f[C]dotnet\ tool\ list\ \-\-tool\-path\ ~/bin\f[]
.SS See also
.PP
\&.NET Core Global Tools
.SH AUTHORS
mairaw.

64
Documentation/manpages/sdk/dotnet-tool-uninstall.1 Normal file
View file

@ -0,0 +1,64 @@
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet tool uninstall command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
.SH dotnet tool uninstall
.PP
.SH NAME
.PP
\f[C]dotnet\ tool\ uninstall\f[] \- Uninstalls the specified .NET Core Global Tool from your machine.
.SH SYNOPSIS
.IP
.nf
\f[C]
dotnet\ tool\ uninstall\ <PACKAGE_NAME>\ <\-g|\-\-global>
dotnet\ tool\ uninstall\ <PACKAGE_NAME>\ <\-\-tool\-path>
dotnet\ tool\ uninstall\ <\-h|\-\-help>
\f[]
.fi
.SH DESCRIPTION
.PP
The \f[C]dotnet\ tool\ uninstall\f[] command provides a way for you to uninstall .NET Core Global Tools from your machine.
To use the command, you either have to specify that you want to remove a user\-wide tool using the \f[C]\-\-global\f[] option or specify a path to where the tool is installed using the \f[C]\-\-tool\-path\f[] option.
.SS Arguments
.PP
\f[C]PACKAGE_NAME\f[]
.PP
Name/ID of the NuGet package that contains the .NET Core Global Tool to uninstall.
You can find the package name using the dotnet tool list command.
.SH OPTIONS
.PP
\f[C]\-g|\-\-global\f[]
.PP
Specifies that the tool to be removed is from a user\-wide installation.
Can't be combined with the \f[C]\-\-tool\-path\f[] option.
If you don't specify this option, you must specify the \f[C]\-\-tool\-path\f[] option.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-\-tool\-path\ <PATH>\f[]
.PP
Specifies the location where to uninstall the Global Tool.
PATH can be absolute or relative.
Can't be combined with the \f[C]\-\-global\f[] option.
If you don't specify this option, you must specify the \f[C]\-\-global\f[] option.
.SH EXAMPLES
.PP
Uninstalls the dotnetsay Global Tool:
.PP
\f[C]dotnet\ tool\ uninstall\ \-g\ dotnetsay\f[]
.PP
Uninstalls the dotnetsay Global Tool from a specific Windows folder:
.PP
\f[C]dotnet\ tool\ uninstall\ dotnetsay\ \-\-tool\-path\ c:\\global\-tools\f[]
.PP
Uninstalls the dotnetsay Global Tool from a specific Linux/macOS folder:
.PP
\f[C]dotnet\ tool\ uninstall\ dotnetsay\ \-\-tool\-path\ ~/bin\f[]
.SS See also
.PP
\&.NET Core Global Tools
.SH AUTHORS
mairaw.

82
Documentation/manpages/sdk/dotnet-tool-update.1 Normal file
View file

@ -0,0 +1,82 @@
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet tool update command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
.SH dotnet tool update
.PP
.SH NAME
.PP
\f[C]dotnet\ tool\ update\f[] \- Updates the specified .NET Core Global Tool on your machine.
.SH SYNOPSIS
.IP
.nf
\f[C]
dotnet\ tool\ update\ <PACKAGE_NAME>\ <\-g|\-\-global>\ [\-\-configfile]\ [\-\-framework]\ [\-v|\-\-verbosity]
dotnet\ tool\ update\ <PACKAGE_NAME>\ <\-\-tool\-path>\ [\-\-configfile]\ [\-\-framework]\ [\-v|\-\-verbosity]
dotnet\ tool\ update\ <\-h|\-\-help>
\f[]
.fi
.SH DESCRIPTION
.PP
The \f[C]dotnet\ tool\ update\f[] command provides a way for you to update .NET Core Global Tools on your machine to the latest stable version of the package.
The command uninstalls and reinstalls a tool, effectively updating it.
To use the command, you either have to specify that you want to update a tool from a user\-wide installation using the \f[C]\-\-global\f[] option or specify a path to where the tool is installed using the \f[C]\-\-tool\-path\f[] option.
.SS Arguments
.PP
\f[C]PACKAGE_NAME\f[]
.PP
Name/ID of the NuGet package that contains the .NET Core Global Tool to update.
You can find the package name using the dotnet tool list command.
.SH OPTIONS
.PP
\f[C]\-\-add\-source\ <SOURCE>\f[]
.PP
Adds an additional NuGet package source to use during installation.
.PP
\f[C]\-\-configfile\ <FILE>\f[]
.PP
The NuGet configuration (\f[I]nuget.config\f[]) file to use.
.PP
\f[C]\-\-framework\ <FRAMEWORK>\f[]
.PP
Specifies the target framework to update the tool for.
.PP
\f[C]\-g|\-\-global\f[]
.PP
Specifies that the update is for a user\-wide tool.
Can't be combined with the \f[C]\-\-tool\-path\f[] option.
If you don't specify this option, you must specify the \f[C]\-\-tool\-path\f[] option.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-\-tool\-path\ <PATH>\f[]
.PP
Specifies the location where the Global Tool is installed.
PATH can be absolute or relative.
Can't be combined with the \f[C]\-\-global\f[] option.
If you don't specify this option, you must specify the \f[C]\-\-global\f[] option.
.PP
\f[C]\-v|\-\-verbosity\ <LEVEL>\f[]
.PP
Sets the verbosity level of the command.
Allowed values are \f[C]q[uiet]\f[], \f[C]m[inimal]\f[], \f[C]n[ormal]\f[], \f[C]d[etailed]\f[], and \f[C]diag[nostic]\f[].
.SH EXAMPLES
.PP
Updates the dotnetsay Global Tool:
.PP
\f[C]dotnet\ tool\ update\ \-g\ dotnetsay\f[]
.PP
Updates the dotnetsay Global Tool located on a specific Windows folder:
.PP
\f[C]dotnet\ tool\ update\ dotnetsay\ \-\-tool\-path\ c:\\global\-tools\f[]
.PP
Updates the dotnetsay Global Tool located on a specific Linux/macOS folder:
.PP
\f[C]dotnet\ tool\ update\ dotnetsay\ \-\-tool\-path\ ~/bin\f[]
.SS See also
.PP
\&.NET Core Global Tools
.SH AUTHORS
mairaw.

250
Documentation/manpages/sdk/dotnet-vstest.1
View file

@ -1,4 +1,4 @@
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet vstest command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -8,8 +8,36 @@
.PP
\f[C]dotnet\-vstest\f[] \- Runs tests from the specified files.
.SH SYNOPSIS
.SS .NET Core 2.1
.IP
.nf
\f[C]
dotnet\ vstest\ [<TEST_FILE_NAMES>]\ [\-\-Settings|/Settings]\ [\-\-Tests|/Tests]\ [\-\-TestAdapterPath|/TestAdapterPath]
\ \ \ \ [\-\-Platform|/Platform]\ [\-\-Framework|/Framework]\ [\-\-Parallel|/Parallel]\ [\-\-TestCaseFilter|/TestCaseFilter]\ [\-\-logger|/logger]
\ \ \ \ [\-lt|\-\-ListTests|/lt|/ListTests]\ [\-\-ParentProcessId|/ParentProcessId]\ [\-\-Port|/Port]\ [\-\-Diag|/Diag]\ [\-\-Blame|/Blame]\ [\-\-InIsolation|/InIsolation]
\ \ \ \ [[\-\-]\ <args>...]]\ [\-?|\-\-Help|/?|/Help]
\f[]
.fi
.SS .NET Core 2.0
.IP
.nf
\f[C]
dotnet\ vstest\ [<TEST_FILE_NAMES>]\ [\-\-Settings|/Settings]\ [\-\-Tests|/Tests]\ [\-\-TestAdapterPath|/TestAdapterPath]\
\ \ \ \ [\-\-Platform|/Platform]\ [\-\-Framework|/Framework]\ [\-\-Parallel|/Parallel]\ [\-\-TestCaseFilter|/TestCaseFilter]\ [\-\-logger|/logger]
\ \ \ \ [\-lt|\-\-ListTests|/lt|/ListTests]\ [\-\-ParentProcessId|/ParentProcessId]\ [\-\-Port|/Port]\ [\-\-Diag|/Diag]\ [[\-\-]\ <args>...]]\ [\-?|\-\-Help|/?|/Help]
\f[]
.fi
.SS .NET Core 1.x
.IP
.nf
\f[C]
dotnet\ vstest\ [<TEST_FILE_NAMES>]\ [\-\-Settings|/Settings]\ [\-\-Tests|/Tests]\ [\-\-TestAdapterPath|/TestAdapterPath]
\ \ \ \ [\-\-Platform|/Platform]\ [\-\-Framework|/Framework]\ [\-\-Parallel|/Parallel]\ [\-\-TestCaseFilter|/TestCaseFilter]\ [\-\-logger|/logger]\
\ \ \ \ [\-lt|\-\-ListTests|/lt|/ListTests]\ [\-\-ParentProcessId|/ParentProcessId]\ [\-\-Port|/Port]\ [\-\-Diag|/Diag]\ [[\-\-]\ <args>...]]\ [\-?|\-\-Help|/?|/Help]
\f[]
.fi
.PP
\f[C]dotnet\ vstest\ [<TEST_FILE_NAMES>]\ [\-\-Settings|/Settings]\ [\-\-Tests|/Tests]\ [\-\-TestAdapterPath|/TestAdapterPath]\ [\-\-Platform|/Platform]\ [\-\-Framework|/Framework]\ [\-\-Parallel|/Parallel]\ [\-\-TestCaseFilter|/TestCaseFilter]\ [\-\-logger|/logger]\ [\-lt|\-\-ListTests|/lt|/ListTests]\ [\-\-ParentProcessId|/ParentProcessId]\ [\-\-Port|/Port]\ [\-\-Diag|/Diag]\ [[\-\-]\ <args>...]]\ [\-?|\-\-Help|/?|/Help]\f[]
* * * * *
.SH DESCRIPTION
.PP
The \f[C]dotnet\-vstest\f[] command runs the \f[C]VSTest.Console\f[] command\-line application to run automated unit and coded UI application tests.
@ -20,6 +48,7 @@ The \f[C]dotnet\-vstest\f[] command runs the \f[C]VSTest.Console\f[] command\-li
Run tests from the specified assemblies.
Separate multiple test assembly names with spaces.
.SH OPTIONS
.SS .NET Core 2.1
.PP
\f[C]\-\-Settings|/Settings:<Settings\ File>\f[]
.PP
@ -42,7 +71,119 @@ Valid values are \f[C]x86\f[], \f[C]x64\f[], and \f[C]ARM\f[].
\f[C]\-\-Framework|/Framework:<Framework\ Version>\f[]
.PP
Target .NET Framework version used for test execution.
Examples of valid values are \f[C]\&.NETFramework,Version=v4.6\f[], \f[C]\&.NETCoreApp,Version=v1.0\f[], etc.
Examples of valid values are \f[C]\&.NETFramework,Version=v4.6\f[] or \f[C]\&.NETCoreApp,Version=v1.0\f[].
Other supported values are \f[C]Framework35\f[], \f[C]Framework40\f[], \f[C]Framework45\f[], \f[C]FrameworkCore10\f[], and \f[C]FrameworkUap10\f[].
.PP
\f[C]\-\-Parallel|/Parallel\f[]
.PP
Execute tests in parallel.
By default, all available cores on the machine are available for use.
Set an explicit number of cores with a settings file.
.PP
\f[C]\-\-TestCaseFilter|/TestCaseFilter:<Expression>\f[]
.PP
Run tests that match the given expression.
\f[C]<Expression>\f[] is of the format \f[C]<property>Operator<value>[|&<Expression>]\f[], where Operator is one of \f[C]=\f[], \f[C]!=\f[], or \f[C]~\f[].
Operator \f[C]~\f[] has `contains' semantics and is applicable for string properties like \f[C]DisplayName\f[].
Parenthesis \f[C]()\f[] are used to group sub\-expressions.
.PP
\f[C]\-?|\-\-Help|/?|/Help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-\-logger|/logger:<Logger\ Uri/FriendlyName>\f[]
.PP
Specify a logger for test results.
.IP \[bu] 2
To publish test results to Team Foundation Server, use the \f[C]TfsPublisher\f[] logger provider:
.RS 2
.IP
.nf
\f[C]
/logger:TfsPublisher;
\ \ \ \ Collection=<team\ project\ collection\ url>;
\ \ \ \ BuildName=<build\ name>;
\ \ \ \ TeamProject=<team\ project\ name>
\ \ \ \ [;Platform=<Defaults\ to\ "Any\ CPU">]
\ \ \ \ [;Flavor=<Defaults\ to\ "Debug">]
\ \ \ \ [;RunTitle=<title>]
\f[]
.fi
.RE
.IP \[bu] 2
To log results to a Visual Studio Test Results File (TRX), use the \f[C]trx\f[] logger provider.
This switch creates a file in the test results directory with given log file name.
If \f[C]LogFileName\f[] isn't provided, a unique file name is created to hold the test results.
.RS 2
.IP
.nf
\f[C]
/logger:trx\ [;LogFileName=<Defaults\ to\ unique\ file\ name>]
\f[]
.fi
.RE
.PP
\f[C]\-lt|\-\-ListTests|/lt|/ListTests:<File\ Name>\f[]
.PP
Lists all discovered tests from the given test container.
.PP
\f[C]\-\-ParentProcessId|/ParentProcessId:<ParentProcessId>\f[]
.PP
Process ID of the parent process responsible for launching the current process.
.PP
\f[C]\-\-Port|/Port:<Port>\f[]
.PP
Specifies the port for the socket connection and receiving the event messages.
.PP
\f[C]\-\-Diag|/Diag:<Path\ to\ log\ file>\f[]
.PP
Enables verbose logs for the test platform.
Logs are written to the provided file.
.PP
\f[C]\-\-Blame|/Blame\f[]
.PP
Runs the tests in blame mode.
This option is helpful in isolating the problematic tests causing test host to crash.
It creates an output file in the current directory as \f[I]Sequence.xml\f[] that captures the order of tests execution before the crash.
.PP
\f[C]\-\-InIsolation|/InIsolation\f[]
.PP
Runs the tests in an isolated process.
This makes \f[I]vstest.console.exe\f[] process less likely to be stopped on an error in the tests, but tests may run slower.
.PP
\f[C]\@<file>\f[]
.PP
Reads response file for more options.
.PP
\f[C]args\f[]
.PP
Specifies extra arguments to pass to the adapter.
Arguments are specified as name\-value pairs of the form \f[C]<n>=<v>\f[], where \f[C]<n>\f[] is the argument name and \f[C]<v>\f[] is the argument value.
Use a space to separate multiple arguments.
.SS .NET Core 2.0
.PP
\f[C]\-\-Settings|/Settings:<Settings\ File>\f[]
.PP
Settings to use when running tests.
.PP
\f[C]\-\-Tests|/Tests:<Test\ Names>\f[]
.PP
Run tests with names that match the provided values.
Separate multiple values with commas.
.PP
\f[C]\-\-TestAdapterPath|/TestAdapterPath\f[]
.PP
Use custom test adapters from a given path (if any) in the test run.
.PP
\f[C]\-\-Platform|/Platform:<Platform\ type>\f[]
.PP
Target platform architecture used for test execution.
Valid values are \f[C]x86\f[], \f[C]x64\f[], and \f[C]ARM\f[].
.PP
\f[C]\-\-Framework|/Framework:<Framework\ Version>\f[]
.PP
Target .NET Framework version used for test execution.
Examples of valid values are \f[C]\&.NETFramework,Version=v4.6\f[] or \f[C]\&.NETCoreApp,Version=v1.0\f[].
Other supported values are \f[C]Framework35\f[], \f[C]Framework40\f[], \f[C]Framework45\f[], and \f[C]FrameworkCore10\f[].
.PP
\f[C]\-\-Parallel|/Parallel\f[]
@ -96,11 +237,11 @@ If \f[C]LogFileName\f[] isn't provided, a unique file name is created to hold th
.PP
\f[C]\-lt|\-\-ListTests|/lt|/ListTests:<File\ Name>\f[]
.PP
Lists discovered tests from the given test container.
Lists all discovered tests from the given test container.
.PP
\f[C]\-\-ParentProcessId|/ParentProcessId:<ParentProcessId>\f[]
.PP
Process Id of the parent process responsible for launching the current process.
Process ID of the parent process responsible for launching the current process.
.PP
\f[C]\-\-Port|/Port:<Port>\f[]
.PP
@ -116,6 +257,105 @@ Logs are written to the provided file.
Specifies extra arguments to pass to the adapter.
Arguments are specified as name\-value pairs of the form \f[C]<n>=<v>\f[], where \f[C]<n>\f[] is the argument name and \f[C]<v>\f[] is the argument value.
Use a space to separate multiple arguments.
.SS .NET Core 1.x
.PP
\f[C]\-\-Settings|/Settings:<Settings\ File>\f[]
.PP
Settings to use when running tests.
.PP
\f[C]\-\-Tests|/Tests:<Test\ Names>\f[]
.PP
Run tests with names that match the provided values.
Separate multiple values with commas.
.PP
\f[C]\-\-TestAdapterPath|/TestAdapterPath\f[]
.PP
Use custom test adapters from a given path (if any) in the test run.
.PP
\f[C]\-\-Platform|/Platform:<Platform\ type>\f[]
.PP
Target platform architecture used for test execution.
Valid values are \f[C]x86\f[], \f[C]x64\f[], and \f[C]ARM\f[].
.PP
\f[C]\-\-Framework|/Framework:<Framework\ Version>\f[]
.PP
Target .NET Framework version used for test execution.
Examples of valid values are \f[C]\&.NETFramework,Version=v4.6\f[] or \f[C]\&.NETCoreApp,Version=v1.0\f[].
Other supported values are \f[C]Framework35\f[], \f[C]Framework40\f[], \f[C]Framework45\f[], and \f[C]FrameworkCore10\f[].
.PP
\f[C]\-\-Parallel|/Parallel\f[]
.PP
Execute tests in parallel.
By default, all available cores on the machine are available for use.
Set an explicit number of cores with a settings file.
.PP
\f[C]\-\-TestCaseFilter|/TestCaseFilter:<Expression>\f[]
.PP
Run tests that match the given expression.
\f[C]<Expression>\f[] is of the format \f[C]<property>Operator<value>[|&<Expression>]\f[], where Operator is one of \f[C]=\f[], \f[C]!=\f[], or \f[C]~\f[].
Operator \f[C]~\f[] has `contains' semantics and is applicable for string properties like \f[C]DisplayName\f[].
Parenthesis \f[C]()\f[] are used to group sub\-expressions.
.PP
\f[C]\-?|\-\-Help|/?|/Help\f[]
.PP
Prints out a short help for the command.
.PP
\f[C]\-\-logger|/logger:<Logger\ Uri/FriendlyName>\f[]
.PP
Specify a logger for test results.
.IP \[bu] 2
To publish test results to Team Foundation Server, use the \f[C]TfsPublisher\f[] logger provider:
.RS 2
.IP
.nf
\f[C]
/logger:TfsPublisher;
\ \ \ \ Collection=<team\ project\ collection\ url>;
\ \ \ \ BuildName=<build\ name>;
\ \ \ \ TeamProject=<team\ project\ name>
\ \ \ \ [;Platform=<Defaults\ to\ "Any\ CPU">]
\ \ \ \ [;Flavor=<Defaults\ to\ "Debug">]
\ \ \ \ [;RunTitle=<title>]
\f[]
.fi
.RE
.IP \[bu] 2
To log results to a Visual Studio Test Results File (TRX), use the \f[C]trx\f[] logger provider.
This switch creates a file in the test results directory with given log file name.
If \f[C]LogFileName\f[] isn't provided, a unique file name is created to hold the test results.
.RS 2
.IP
.nf
\f[C]
/logger:trx\ [;LogFileName=<Defaults\ to\ unique\ file\ name>]
\f[]
.fi
.RE
.PP
\f[C]\-lt|\-\-ListTests|/lt|/ListTests:<File\ Name>\f[]
.PP
Lists all discovered tests from the given test container.
.PP
\f[C]\-\-ParentProcessId|/ParentProcessId:<ParentProcessId>\f[]
.PP
Process ID of the parent process responsible for launching the current process.
.PP
\f[C]\-\-Port|/Port:<Port>\f[]
.PP
Specifies the port for the socket connection and receiving the event messages.
.PP
\f[C]\-\-Diag|/Diag:<Path\ to\ log\ file>\f[]
.PP
Enables verbose logs for the test platform.
Logs are written to the provided file.
.PP
\f[C]args\f[]
.PP
Specifies extra arguments to pass to the adapter.
Arguments are specified as name\-value pairs of the form \f[C]<n>=<v>\f[], where \f[C]<n>\f[] is the argument name and \f[C]<v>\f[] is the argument value.
Use a space to separate multiple arguments.
.PP
* * * * *
.SH EXAMPLES
.PP
Run tests in \f[C]mytestproject.dll\f[]:

279
Documentation/manpages/sdk/dotnet.1
View file

@ -1,5 +1,5 @@
.\"t
.\" Automatically generated by Pandoc 2.1.3
.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "dotnet command \- .NET Core CLI" "1" "" "" ".NET Core"
.hy
@ -9,7 +9,15 @@
.PP
\f[C]dotnet\f[] \- General driver for running the command\-line commands.
.SH SYNOPSIS
.SS .NET Core 2.x
.SS .NET Core 2.1
.IP
.nf
\f[C]
dotnet\ [command]\ [arguments]\ [\-\-additional\-deps]\ [\-\-additionalprobingpath]\ [\-d|\-\-diagnostics]\ [\-\-fx\-version]
\ \ \ \ [\-h|\-\-help]\ [\-\-info]\ [\-\-list\-runtimes]\ [\-\-list\-sdks]\ [\-\-roll\-forward\-on\-no\-candidate\-fx]\ [\-v|\-\-verbosity]\ [\-\-version]
\f[]
.fi
.SS .NET Core 2.0
.IP
.nf
\f[C]
@ -33,13 +41,61 @@ dotnet\ [command]\ [arguments]\ [\-\-additionalprobingpath]\ [\-d|\-\-diagnostic
Invoked on its own, it provides brief usage instructions.
.PP
Each specific feature is implemented as a command.
In order to use the feature, the command is specified after \f[C]dotnet\f[], such as \f[C]dotnet\ build\f[].
To use the feature, the command is specified after \f[C]dotnet\f[], such as \f[C]dotnet\ build\f[].
All of the arguments following the command are its own arguments.
.PP
The only time \f[C]dotnet\f[] is used as a command on its own is to run framework\-dependent apps.
Specify an application DLL after the \f[C]dotnet\f[] verb to execute the application (for example, \f[C]dotnet\ myapp.dll\f[]).
.SH OPTIONS
.SS .NET Core 2.x
.SS .NET Core 2.1
.PP
\f[C]\-\-additional\-deps\ <PATH>\f[]
.PP
Path to additional \f[I]deps.json\f[] file.
.PP
\f[C]\-\-additionalprobingpath\ <PATH>\f[]
.PP
Path containing probing policy and assemblies to probe.
.PP
\f[C]\-d|\-\-diagnostics\f[]
.PP
Enables diagnostic output.
.PP
\f[C]\-\-fx\-version\ <VERSION>\f[]
.PP
Version of the installed .NET Core runtime to use to run the application.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Prints out a short help for the command.
If using with \f[C]dotnet\f[], it also prints a list of the available commands.
.PP
\f[C]\-\-info\f[]
.PP
Prints out detailed information about the CLI tooling and the environment, such as the current operating system, commit SHA for the version, and other information.
.PP
\f[C]\-\-list\-runtimes\f[]
.PP
Displays the installed .NET Core runtimes.
.PP
\f[C]\-\-list\-sdks\f[]
.PP
Displays the installed .NET Core SDKs.
.PP
\f[C]\-\-roll\-forward\-on\-no\-candidate\-fx\f[]
.PP
Rolls forward on no candidate shared framework.
.PP
\f[C]\-v|\-\-verbosity\ <LEVEL>\f[]
.PP
Sets the verbosity level of the command.
Allowed values are \f[C]q[uiet]\f[], \f[C]m[inimal]\f[], \f[C]n[ormal]\f[], \f[C]d[etailed]\f[], and \f[C]diag[nostic]\f[].
Not supported in every command; see specific command page to determine if this option is available.
.PP
\f[C]\-\-version\f[]
.PP
Prints out the version of the .NET Core SDK in use.
.SS .NET Core 2.0
.PP
\f[C]\-\-additional\-deps\ <PATH>\f[]
.PP
@ -115,7 +171,89 @@ Prints out the version of the .NET Core SDK in use.
* * * * *
.SS dotnet commands
.SS General
.SS .NET Core 2.x
.SS .NET Core 2.1
.PP
.TS
tab(@);
l l.
T{
Command
T}@T{
Function
T}
_
T{
dotnet build
T}@T{
Builds a .NET Core application.
T}
T{
dotnet build\-server
T}@T{
Interacts with servers started by a build.
T}
T{
dotnet clean
T}@T{
Clean build outputs.
T}
T{
dotnet help
T}@T{
Shows more detailed documentation online for the command.
T}
T{
dotnet migrate
T}@T{
Migrates a valid Preview 2 project to a .NET Core SDK 1.0 project.
T}
T{
dotnet msbuild
T}@T{
Provides access to the MSBuild command line.
T}
T{
dotnet new
T}@T{
Initializes a C# or F# project for a given template.
T}
T{
dotnet pack
T}@T{
Creates a NuGet package of your code.
T}
T{
dotnet publish
T}@T{
Publishes a .NET framework\-dependent or self\-contained application.
T}
T{
dotnet restore
T}@T{
Restores the dependencies for a given application.
T}
T{
dotnet run
T}@T{
Runs the application from source.
T}
T{
dotnet sln
T}@T{
Options to add, remove, and list projects in a solution file.
T}
T{
dotnet store
T}@T{
Stores assemblies in the runtime package store.
T}
T{
dotnet test
T}@T{
Runs tests using a test runner.
T}
.TE
.SS .NET Core 2.0
.PP
.TS
tab(@);
@ -275,17 +413,17 @@ _
T{
dotnet add reference
T}@T{
Add a project reference.
Adds a project reference.
T}
T{
dotnet list reference
T}@T{
List project references.
Lists project references.
T}
T{
dotnet remove reference
T}@T{
Remove a project reference.
Removes a project reference.
T}
.TE
.SS NuGet packages
@ -302,12 +440,12 @@ _
T{
dotnet add package
T}@T{
Add a NuGet package.
Adds a NuGet package.
T}
T{
dotnet remove package
T}@T{
Remove a NuGet package.
Removes a NuGet package.
T}
.TE
.SS NuGet commands
@ -337,9 +475,85 @@ T}@T{
Pushes a package to the server and publishes it.
T}
.TE
.SS Global Tools commands
.PP
\&.NET Core Global Tools are available strating with .NET Core SDK 2.1.300:
.PP
.TS
tab(@);
l l.
T{
Command
T}@T{
Function
T}
_
T{
dotnet tool install
T}@T{
Installs a Global Tool on your machine.
T}
T{
dotnet tool list
T}@T{
Lists all Global Tools currently installed in the default directory on your machine or in the specified path.
T}
T{
dotnet tool uninstall
T}@T{
Uninstalls a Global Tool from your machine.
T}
T{
dotnet tool update
T}@T{
Updates a Global Tool on your machine.
T}
.TE
.SS Additional tools
.PP
Starting with .NET Core SDK 2.1.300, a number of tools that were available only on a per project basis using \f[C]DotnetCliToolReference\f[] are now available as part of the .NET Core SDK.
These tools include:
.PP
.TS
tab(@);
l l.
T{
Tool
T}@T{
Function
T}
_
T{
dev\-certs
T}@T{
Creates and manages development certificates.
T}
T{
ef
T}@T{
Entity Framework Core command\-line tools.
T}
T{
sql\-cache
T}@T{
SQL Server cache command\-line tools.
T}
T{
user\-secrets
T}@T{
Manages development user secrets.
T}
T{
watch
T}@T{
Starts a file watcher that runs a command when files change.
T}
.TE
.PP
For more information about each tool, execute \f[C]dotnet\ <tool\-name>\ \-\-help\f[].
.SH EXAMPLES
.PP
Initialize a sample .NET Core console application that can be compiled and run:
Creates a new .NET Core console application:
.PP
\f[C]dotnet\ new\ console\f[]
.PP
@ -356,7 +570,7 @@ Run a framework\-dependent app named \f[C]myapp.dll\f[]:
.PP
\f[C]dotnet\ myapp.dll\f[]
.SH ENVIRONMENT VARIABLES
.SS .NET Core 2.x
.SS .NET Core 2.1
.PP
\f[C]DOTNET_PACKAGES\f[]
.PP
@ -370,12 +584,42 @@ Specifies the location of the servicing index to use by the shared host when loa
\f[C]DOTNET_CLI_TELEMETRY_OPTOUT\f[]
.PP
Specifies whether data about the .NET Core tools usage is collected and sent to Microsoft.
Set to \f[C]true\f[] to opt\-out of the telemetry feature (values \f[C]true\f[], \f[C]1\f[], or \f[C]yes\f[] accepted); otherwise, set to \f[C]false\f[] to opt\-in to the telemetry features (values \f[C]false\f[], \f[C]0\f[], or \f[C]no\f[] accepted).
If not set, the defaults is \f[C]false\f[], and the telemetry feature is active.
Set to \f[C]true\f[] to opt\-out of the telemetry feature (values \f[C]true\f[], \f[C]1\f[], or \f[C]yes\f[] accepted).
Otherwise, set to \f[C]false\f[] to opt into the telemetry features (values \f[C]false\f[], \f[C]0\f[], or \f[C]no\f[] accepted).
If not set, the default is \f[C]false\f[] and the telemetry feature is active.
.PP
\f[C]DOTNET_MULTILEVEL_LOOKUP\f[]
.PP
Specifies whether .NET Core runtime, shared framework or SDK are resolved from the global location.
Specifies whether .NET Core runtime, shared framework, or SDK are resolved from the global location.
If not set, it defaults to \f[C]true\f[].
Set to \f[C]false\f[] to not resolve from the global location and have isolated .NET Core installations (values \f[C]0\f[] or \f[C]false\f[] are accepted).
For more information about multi\-level lookup, see Multi\-level SharedFX Lookup.
.PP
\f[C]DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX\f[]
.PP
Disables minor version roll forward.
For more information, see Roll forward.
.SS .NET Core 2.0
.PP
\f[C]DOTNET_PACKAGES\f[]
.PP
The primary package cache.
If not set, it defaults to \f[C]$HOME/.nuget/packages\f[] on Unix or \f[C]%HOME%\\NuGet\\Packages\f[] on Windows.
.PP
\f[C]DOTNET_SERVICING\f[]
.PP
Specifies the location of the servicing index to use by the shared host when loading the runtime.
.PP
\f[C]DOTNET_CLI_TELEMETRY_OPTOUT\f[]
.PP
Specifies whether data about the .NET Core tools usage is collected and sent to Microsoft.
Set to \f[C]true\f[] to opt\-out of the telemetry feature (values \f[C]true\f[], \f[C]1\f[], or \f[C]yes\f[] accepted).
Otherwise, set to \f[C]false\f[] to opt into the telemetry features (values \f[C]false\f[], \f[C]0\f[], or \f[C]no\f[] accepted).
If not set, the default is \f[C]false\f[] and the telemetry feature is active.
.PP
\f[C]DOTNET_MULTILEVEL_LOOKUP\f[]
.PP
Specifies whether .NET Core runtime, shared framework, or SDK are resolved from the global location.
If not set, it defaults to \f[C]true\f[].
Set to \f[C]false\f[] to not resolve from the global location and have isolated .NET Core installations (values \f[C]0\f[] or \f[C]false\f[] are accepted).
For more information about multi\-level lookup, see Multi\-level SharedFX Lookup.
@ -393,8 +637,9 @@ Specifies the location of the servicing index to use by the shared host when loa
\f[C]DOTNET_CLI_TELEMETRY_OPTOUT\f[]
.PP
Specifies whether data about the .NET Core tools usage is collected and sent to Microsoft.
Set to \f[C]true\f[] to opt\-out of the telemetry feature (values \f[C]true\f[], \f[C]1\f[], or \f[C]yes\f[] accepted); otherwise, set to \f[C]false\f[] to opt\-in to the telemetry features (values \f[C]false\f[], \f[C]0\f[], or \f[C]no\f[] accepted).
If not set, the defaults is \f[C]false\f[], and the telemetry feature is active.
Set to \f[C]true\f[] to opt\-out of the telemetry feature (values \f[C]true\f[], \f[C]1\f[], or \f[C]yes\f[] accepted).
Otherwise, set to \f[C]false\f[] to opt into the telemetry features (values \f[C]false\f[], \f[C]0\f[], or \f[C]no\f[] accepted).
If not set, the default is \f[C]false\f[] and the telemetry feature is active.
.PP
* * * * *
.SH AUTHORS

62
README.md
View file

@ -9,7 +9,7 @@ Looking for V1 of the .NET Core tooling?
If you are looking for the v2.0 release of the .NET Core tools (CLI, MSBuild and the new csproj), head over to https://dot.net/core and download!
> **Note:** the release/2.1.3xx branch of the CLI repo is based on an upcoming update of the SDK and is considered pre-release. For production-level usage, please use the
> **Note:** the release/2.1.4xx branch of the CLI repo is based on an upcoming update of the SDK and is considered pre-release. For production-level usage, please use the
> released version of the tools available at https://dot.net/core
Found an issue?
@ -65,7 +65,7 @@ To download the .NET Core runtime **without** the SDK, visit https://github.com/
> want to install the latest released versions, check out the [preceding section](#looking-for-v1-of-the-net-core-tooling).
> In order to be able to restore these pre-release packages, you may need to add a NuGet feed pointing to https://dotnet.myget.org/F/dotnet-core/api/v3/index.json. Other feeds may also be necessary depending on what kind of project you are working with.
| Platform | Latest Daily Build<br>*release/2.1.3xx*<br>[![][version-badge]][version] |
| Platform | Latest Daily Build<br>*release/2.1.4xx*<br>[![][version-badge]][version] |
| -------- | :-------------------------------------: |
| **Windows x64** | [Installer][win-x64-installer] - [Checksum][win-x64-installer-checksum]<br>[zip][win-x64-zip] - [Checksum][win-x64-zip-checksum] |
| **Windows x86** | [Installer][win-x86-installer] - [Checksum][win-x86-installer-checksum]<br>[zip][win-x86-zip] - [Checksum][win-x86-zip-checksum] |
@ -76,7 +76,7 @@ To download the .NET Core runtime **without** the SDK, visit https://github.com/
| **RHEL 6** | [tar.gz][rhel-6-targz] - [Checksum][rhel-6-targz-checksum] |
| **Linux-musl** | [tar.gz][linux-musl-targz] - [Checksum][linux-musl-targz-checksum] |
| Latest Coherent Build<sup>2</sup><br>*release/2.1.3xx* |
| Latest Coherent Build<sup>2</sup><br>*release/2.1.4xx* |
|:------:|
| [![][coherent-version-badge]][coherent-version] |
@ -84,44 +84,44 @@ Reference notes:
> **1**: *Our Debian packages are put together slightly differently than the other OS specific installers. Instead of combining everything, we have separate component packages that depend on each other. If you're installing these directly from the .deb files (via dpkg or similar), then you'll need to install the [corresponding Host, Host FX Resolver, and Shared Framework packages](https://github.com/dotnet/core-setup#daily-builds) before installing the Sdk package.*
> <br><br>**2**: *A 'coherent' build is defined as a build where the Runtime version matches between the CLI and Asp.NET.*
[version]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/latest.version
[coherent-version]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/latest.coherent.version
[version]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/latest.version
[coherent-version]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/latest.coherent.version
[comment]: # (The latest versions are always the same across all platforms. Just need one to show, so picking win-x64's svg.)
[version-badge]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/win_x64_Release_version_badge.svg
[coherent-version-badge]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/win_x64_Release_coherent_badge.svg
[version-badge]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/win_x64_Release_version_badge.svg
[coherent-version-badge]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/win_x64_Release_coherent_badge.svg
[win-x64-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-win-x64.exe
[win-x64-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-win-x64.exe.sha
[win-x64-zip]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-win-x64.zip
[win-x64-zip-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-win-x64.zip.sha
[win-x64-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-win-x64.exe
[win-x64-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-win-x64.exe.sha
[win-x64-zip]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-win-x64.zip
[win-x64-zip-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-win-x64.zip.sha
[win-x86-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-win-x86.exe
[win-x86-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-win-x86.exe.sha
[win-x86-zip]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-win-x86.zip
[win-x86-zip-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-win-x86.zip.sha
[win-x86-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-win-x86.exe
[win-x86-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-win-x86.exe.sha
[win-x86-zip]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-win-x86.zip
[win-x86-zip-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-win-x86.zip.sha
[osx-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-osx-x64.pkg
[osx-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-osx-x64.pkg.sha
[osx-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-osx-x64.tar.gz
[osx-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-osx-x64.tar.gz.sha
[osx-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-osx-x64.pkg
[osx-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-osx-x64.pkg.sha
[osx-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-osx-x64.tar.gz
[osx-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-osx-x64.tar.gz.sha
[linux-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-linux-x64.tar.gz
[linux-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-linux-x64.tar.gz.sha
[linux-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-linux-x64.tar.gz
[linux-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-linux-x64.tar.gz.sha
[linux-arm-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-linux-arm.tar.gz
[linux-arm-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-linux-arm.tar.gz.sha
[linux-arm-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-linux-arm.tar.gz
[linux-arm-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-linux-arm.tar.gz.sha
[linux-arm64-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-linux-arm64.tar.gz
[linux-arm64-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-linux-arm64.tar.gz.sha
[linux-arm64-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-linux-arm64.tar.gz
[linux-arm64-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-linux-arm64.tar.gz.sha
[linux-DEB-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-x64.deb
[linux-DEB-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-x64.deb.sha
[linux-DEB-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-x64.deb
[linux-DEB-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-x64.deb.sha
[linux-RPM-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-x64.rpm
[linux-RPM-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-x64.rpm.sha
[linux-RPM-installer]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-x64.rpm
[linux-RPM-installer-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-x64.rpm.sha
[rhel-6-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-rhel.6-x64.tar.gz
[rhel-6-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-rhel.6-x64.tar.gz.sha
[rhel-6-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-rhel.6-x64.tar.gz
[rhel-6-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.4xx/dotnet-sdk-latest-rhel.6-x64.tar.gz.sha
[linux-musl-targz]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-linux-musl-x64.tar.gz
[linux-musl-targz-checksum]: https://dotnetclichecksums.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/dotnet-sdk-latest-linux-musl-x64.tar.gz.sha

4
build/BranchInfo.props
View file

@ -1,6 +1,6 @@
<Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<Channel>release/2.1.3xx</Channel>
<BranchName>release/2.1.3xx</BranchName>
<Channel>release/2.1.4xx</Channel>
<BranchName>release/2.1.4xx</BranchName>
</PropertyGroup>
</Project>

2
build/BundledTemplates.props
View file

@ -7,5 +7,7 @@
<BundledTemplate Include="Microsoft.DotNet.Web.ItemTemplates" Version="$(MicrosoftNETWebItemTemplatesPackageVersion)" />
<BundledTemplate Include="Microsoft.DotNet.Web.ProjectTemplates.2.1" Version="$(MicrosoftNETWebProjectTemplates21PackageVersion)" />
<BundledTemplate Include="Microsoft.DotNet.Web.Spa.ProjectTemplates" Version="$(MicrosoftNETWebSpaProjectTemplatesPackageVersion)" />
<BundledTemplate Include="NUnit3.DotNetNew.Template" Version="$(NUnit3TemplatesVersion)" />
</ItemGroup>
</Project>

16
build/DependencyVersions.props
View file

@ -12,29 +12,29 @@
<DotnetWatchPackageVersion>2.1.1</DotnetWatchPackageVersion>
<MicrosoftNETCoreAppPackageVersion>2.1.2</MicrosoftNETCoreAppPackageVersion>
<MicrosoftNETCoreDotNetHostResolverPackageVersion>$(MicrosoftNETCoreAppPackageVersion)</MicrosoftNETCoreDotNetHostResolverPackageVersion>
<MicrosoftBuildPackageVersion>15.7.179</MicrosoftBuildPackageVersion>
<MicrosoftBuildPackageVersion>15.8.0-preview-000160</MicrosoftBuildPackageVersion>
<MicrosoftBuildFrameworkPackageVersion>$(MicrosoftBuildPackageVersion)</MicrosoftBuildFrameworkPackageVersion>
<MicrosoftBuildRuntimePackageVersion>$(MicrosoftBuildPackageVersion)</MicrosoftBuildRuntimePackageVersion>
<MicrosoftBuildLocalizationPackageVersion>$(MicrosoftBuildPackageVersion)</MicrosoftBuildLocalizationPackageVersion>
<MicrosoftBuildUtilitiesCorePackageVersion>$(MicrosoftBuildPackageVersion)</MicrosoftBuildUtilitiesCorePackageVersion>
<MicrosoftFSharpCompilerPackageVersion>10.1.4-rtm-180515-0</MicrosoftFSharpCompilerPackageVersion>
<MicrosoftFSharpCompilerPackageVersion>10.2.0-rtm-180620-0</MicrosoftFSharpCompilerPackageVersion>
<MicrosoftCodeAnalysisCSharpPackageVersion>2.8.1-beta6-62915-07</MicrosoftCodeAnalysisCSharpPackageVersion>
<MicrosoftCodeAnalysisBuildTasksPackageVersion>$(MicrosoftCodeAnalysisCSharpPackageVersion)</MicrosoftCodeAnalysisBuildTasksPackageVersion>
<MicrosoftNETCoreCompilersPackageVersion>$(MicrosoftCodeAnalysisCSharpPackageVersion)</MicrosoftNETCoreCompilersPackageVersion>
<MicrosoftCodeAnalysisBuildTasksPackageVersion>$(MicrosoftCodeAnalysisCSharpPackageVersion)</MicrosoftCodeAnalysisBuildTasksPackageVersion>
<MicrosoftNetCompilersNetcorePackageVersion>$(MicrosoftCodeAnalysisCSharpPackageVersion)</MicrosoftNetCompilersNetcorePackageVersion>
<MicrosoftNETSdkPackageVersion>2.1.301</MicrosoftNETSdkPackageVersion>
<MicrosoftNETSdkPackageVersion>2.1.400-preview-63114-01</MicrosoftNETSdkPackageVersion>
<MicrosoftNETBuildExtensionsPackageVersion>$(MicrosoftNETSdkPackageVersion)</MicrosoftNETBuildExtensionsPackageVersion>
<MicrosoftNETSdkRazorPackageVersion>2.1.1</MicrosoftNETSdkRazorPackageVersion>
<MicrosoftNETWebItemTemplatesPackageVersion>2.1.1</MicrosoftNETWebItemTemplatesPackageVersion>
<MicrosoftNETWebProjectTemplates21PackageVersion>2.1.1</MicrosoftNETWebProjectTemplates21PackageVersion>
<MicrosoftNETWebSpaProjectTemplatesPackageVersion>2.1.1</MicrosoftNETWebSpaProjectTemplatesPackageVersion>
<MicrosoftNETSdkWebPackageVersion>2.1.301</MicrosoftNETSdkWebPackageVersion>
<MicrosoftNETSdkWebPackageVersion>2.1.400-preview1-20180705-1834985</MicrosoftNETSdkWebPackageVersion>
<MicrosoftNETSdkPublishPackageVersion>$(MicrosoftNETSdkWebPackageVersion)</MicrosoftNETSdkPublishPackageVersion>
<MicrosoftNETSdkWebProjectSystemPackageVersion>$(MicrosoftNETSdkWebPackageVersion)</MicrosoftNETSdkWebProjectSystemPackageVersion>
<MicrosoftDotNetCommonItemTemplatesPackageVersion>1.0.2-beta3</MicrosoftDotNetCommonItemTemplatesPackageVersion>
<MicrosoftDotNetCommonProjectTemplates20PackageVersion>$(MicrosoftDotNetCommonItemTemplatesPackageVersion)</MicrosoftDotNetCommonProjectTemplates20PackageVersion>
<MicrosoftDotNetTestProjectTemplates20PackageVersion>1.0.2-beta3</MicrosoftDotNetTestProjectTemplates20PackageVersion>
<MicrosoftDotNetTestProjectTemplates20PackageVersion>1.0.2-beta3-20180614-1775839</MicrosoftDotNetTestProjectTemplates20PackageVersion>
<MicrosoftTemplateEngineCliPackageVersion>1.0.2-beta3</MicrosoftTemplateEngineCliPackageVersion>
<MicrosoftTemplateEngineAbstractionsPackageVersion>$(MicrosoftTemplateEngineCliPackageVersion)</MicrosoftTemplateEngineAbstractionsPackageVersion>
<MicrosoftTemplateEngineCliLocalizationPackageVersion>$(MicrosoftTemplateEngineCliPackageVersion)</MicrosoftTemplateEngineCliLocalizationPackageVersion>
@ -46,7 +46,7 @@
<MicrosoftDotNetProjectJsonMigrationPackageVersion>1.3.1</MicrosoftDotNetProjectJsonMigrationPackageVersion>
<MicrosoftDotNetToolsMigrateCommandPackageVersion>$(MicrosoftDotNetProjectJsonMigrationPackageVersion)</MicrosoftDotNetToolsMigrateCommandPackageVersion>
<MicrosoftDotNetArchivePackageVersion>0.2.0-beta-63027-01</MicrosoftDotNetArchivePackageVersion>
<NuGetBuildTasksPackageVersion>4.7.0-rtm.5148</NuGetBuildTasksPackageVersion>
<NuGetBuildTasksPackageVersion>4.8.0-preview5.5328</NuGetBuildTasksPackageVersion>
<NuGetBuildTasksPackPackageVersion>$(NuGetBuildTasksPackageVersion)</NuGetBuildTasksPackPackageVersion>
<NuGetCommonPackageVersion>$(NuGetBuildTasksPackageVersion)</NuGetCommonPackageVersion>
<NuGetCommandLineXPlatPackageVersion>$(NuGetBuildTasksPackageVersion)</NuGetCommandLineXPlatPackageVersion>
@ -55,11 +55,13 @@
<NuGetPackagingPackageVersion>$(NuGetBuildTasksPackageVersion)</NuGetPackagingPackageVersion>
<NuGetProjectModelPackageVersion>$(NuGetBuildTasksPackageVersion)</NuGetProjectModelPackageVersion>
<NuGetVersioningPackageVersion>$(NuGetBuildTasksPackageVersion)</NuGetVersioningPackageVersion>
<MicrosoftNETTestSdkPackageVersion>15.7.0</MicrosoftNETTestSdkPackageVersion>
<NuGetSdkResolverPackageVersion>$(NuGetBuildTasksPackageVersion)</NuGetSdkResolverPackageVersion>
<MicrosoftNETTestSdkPackageVersion>15.8.0</MicrosoftNETTestSdkPackageVersion>
<MicrosoftTestPlatformCLIPackageVersion>$(MicrosoftNETTestSdkPackageVersion)</MicrosoftTestPlatformCLIPackageVersion>
<MicrosoftTestPlatformBuildPackageVersion>$(MicrosoftNETTestSdkPackageVersion)</MicrosoftTestPlatformBuildPackageVersion>
<XliffTasksPackageVersion>0.2.0-beta-000042</XliffTasksPackageVersion>
<MicroBuildCorePackageVersion>0.2.0</MicroBuildCorePackageVersion>
<NUnit3TemplatesVersion>1.5.1</NUnit3TemplatesVersion>
</PropertyGroup>
<!-- NOTE: The property group above is in alignment with orchestrated build version naming conventions. -->

17
build/MSBuildExtensions.targets
View file

@ -132,6 +132,16 @@
<_NETCoreSdkIsPreview Condition=" '$(DropSuffix)' != 'true' ">true</_NETCoreSdkIsPreview>
</PropertyGroup>
<!--
Setting the property to true if patch == 0 and preview == true. SDK will set DefaultNetCorePatchVersion according to this flag.
So that we don't need to manually update the version selection logic between when we ship a final release and when we ship the first patch
-->
<GetUseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion
BundledNETCoreAppPackageVersion="$(BundledNETCoreAppPackageVersion)">
<Output TaskParameter="UseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion"
PropertyName="_UseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion" />
</GetUseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion>
<ItemGroup>
<BundledVersionsVariable Include="BundledAspNetCoreAllTargetFrameworkVersion" Value="$(_AspNetCoreAllTargetFrameworkVersion)" />
<BundledVersionsVariable Include="BundledAspNetCoreAllPackageVersion" Value="$(_AspNetCoreAllPackageVersion)" />
@ -170,6 +180,7 @@ Copyright (c) .NET Foundation. All rights reserved.
<PropertyGroup>
<BundledNETCoreAppTargetFrameworkVersion>$(_NETCoreAppTargetFrameworkVersion)</BundledNETCoreAppTargetFrameworkVersion>
<BundledNETCoreAppPackageVersion>$(_NETCoreAppPackageVersion)</BundledNETCoreAppPackageVersion>
<UseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion>$(_UseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion)</UseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion>
<BundledNETStandardTargetFrameworkVersion>$(_NETStandardTargetFrameworkVersion)</BundledNETStandardTargetFrameworkVersion>
<BundledNETStandardPackageVersion>$(_NETStandardLibraryPackageVersion)</BundledNETStandardPackageVersion>
<BundledNETCorePlatformsPackageVersion>$(_NETCorePlatformsPackageVersion)</BundledNETCorePlatformsPackageVersion>
@ -182,9 +193,9 @@ Copyright (c) .NET Foundation. All rights reserved.
<DefaultPatchVersionForAspNetCoreApp2_1>$(_DefaultPatchVersionForAspNetCoreApp2_1)</DefaultPatchVersionForAspNetCoreApp2_1>
<!-- Latest patch versions for each minor version of .NET Core -->
<LatestPatchVersionForNetCore1_0 Condition="'$(LatestPatchVersionForNetCore1_0)' == ''">1.0.11</LatestPatchVersionForNetCore1_0>
<LatestPatchVersionForNetCore1_1 Condition="'$(LatestPatchVersionForNetCore1_1)' == ''">1.1.8</LatestPatchVersionForNetCore1_1>
<LatestPatchVersionForNetCore2_0 Condition="'$(LatestPatchVersionForNetCore2_0)' == ''">2.0.7</LatestPatchVersionForNetCore2_0>
<LatestPatchVersionForNetCore1_0 Condition="'%24(LatestPatchVersionForNetCore1_0)' == ''">1.0.12</LatestPatchVersionForNetCore1_0>
<LatestPatchVersionForNetCore1_1 Condition="'%24(LatestPatchVersionForNetCore1_1)' == ''">1.1.9</LatestPatchVersionForNetCore1_1>
<LatestPatchVersionForNetCore2_0 Condition="'%24(LatestPatchVersionForNetCore2_0)' == ''">2.0.9</LatestPatchVersionForNetCore2_0>
</PropertyGroup>
</Project>
]]>

1
build/Microsoft.DotNet.Cli.tasks
View file

@ -23,6 +23,7 @@
<UsingTask TaskName="GenerateMsiVersion" AssemblyFile="$(CLIBuildDll)" />
<UsingTask TaskName="GenerateNuGetPackagesArchiveVersion" AssemblyFile="$(CLIBuildDll)" />
<UsingTask TaskName="GetCurrentRuntimeInformation" AssemblyFile="$(CLIBuildDll)" />
<UsingTask TaskName="GetUseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion" AssemblyFile="$(CLIBuildDll)"/>
<UsingTask TaskName="MakeRelative" AssemblyFile="$(CLIBuildDll)" />
<UsingTask TaskName="RemoveAssetFromDepsPackages" AssemblyFile="$(CLIBuildDll)" />
<UsingTask TaskName="ReplaceFileContents" AssemblyFile="$(CLIBuildDll)" />

6
build/NugetConfigFile.targets
View file

@ -20,18 +20,24 @@
<![CDATA[
<add key="BlobFeed" value="https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json" />
<add key="aspnetcore-dev" value="https://dotnet.myget.org/F/aspnetcore-dev/api/v3/index.json" />
<add key="templating" value="https://dotnet.myget.org/F/templating/api/v3/index.json" />
<add key="websdk" value="https://dotnet.myget.org/F/dotnet-web/api/v3/index.json" />
<add key="roslyn" value="https://dotnet.myget.org/f/roslyn/api/v3/index.json" />
<add key="nuget-build" value="https://dotnet.myget.org/F/nuget-build/api/v3/index.json" />
<add key="api.nuget.org" value="https://api.nuget.org/v3/index.json" />
<add key="container-tools" value="https://www.myget.org/F/container-tools-for-visual-studio/api/v3/index.json" />
<add key="linux-musl-bootstrap-feed" value="https://dotnetfeed.blob.core.windows.net/orchestrated-release-2-1/20180420-03/aspnet-inputs/index.json" />
<add key="dotnet-msbuild" value="https://dotnet.myget.org/F/msbuild/api/v3/index.json" />
<add key="myget-vstest" value="https://dotnet.myget.org/F/vstest/api/v3/index.json" />
]]>
</NugetConfigCLIFeeds>
<NugetConfigSuffix>
<![CDATA[
</packageSources>
<disabledPackageSources>
<clear/>
</disabledPackageSources>
</configuration>
]]>
</NugetConfigSuffix>

2
build/Version.props
View file

@ -2,7 +2,7 @@
<PropertyGroup>
<VersionMajor>2</VersionMajor>
<VersionMinor>1</VersionMinor>
<VersionPatch>302</VersionPatch>
<VersionPatch>400</VersionPatch>
<ReleaseSuffix Condition=" '$(ReleaseSuffix)' == '' ">preview</ReleaseSuffix>
<MajorMinorVersion>$(VersionMajor).$(VersionMinor)</MajorMinorVersion>

5
build/package/Installer.MSI.targets
View file

@ -14,6 +14,7 @@
<CombinedFrameworkSdkHostBundleEngineName>$(InstallerOutputDirectory)/$(ArtifactNameWithVersionCombinedHostHostFxrFrameworkSdk)-engine.exe</CombinedFrameworkSdkHostBundleEngineName>
<SdkGenerateMsiPowershellScript>$(RepoRoot)/packaging/windows/clisdk/generatemsi.ps1</SdkGenerateMsiPowershellScript>
<SdkStableFileIdForApphostTransform>$(RepoRoot)/packaging/windows/clisdk/stablefileidforapphosttransform.xslt</SdkStableFileIdForApphostTransform>
<SdkGenerateBundlePowershellScript>$(RepoRoot)/packaging/windows/clisdk/generatebundle.ps1</SdkGenerateBundlePowershellScript>
<SdkGenerateNupkgPowershellScript>$(RepoRoot)/packaging/windows/clisdk/generatenupkg.ps1</SdkGenerateNupkgPowershellScript>
@ -110,7 +111,9 @@
'$(SimpleVersion)'
'$(NugetVersion)'
'$(SdkInstallerUpgradeCode)'
'$(Architecture)'" />
'$(Architecture)'
'$(SdkStableFileIdForApphostTransform)'
" />
</Target>
<Target Name="GenerateMSBuildExtensionsMsi"

30
build_projects/dotnet-cli-build/GetUseBundledVersionAsDefaultVersion.cs Normal file
View file

@ -0,0 +1,30 @@
// Copyright (c) .NET Foundation and contributors. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
using System;
using System.IO;
using Microsoft.Build.Utilities;
using Microsoft.Build.Framework;
using Microsoft.DotNet.Cli.Build.Framework;
using NuGet.Versioning;
namespace Microsoft.DotNet.Cli.Build
{
public class GetUseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion : Task
{
[Required]
public string BundledNETCoreAppPackageVersion { get; set; }
[Output]
public string UseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion { get; set; }
public override bool Execute()
{
var parsedVersion = NuGetVersion.Parse(BundledNETCoreAppPackageVersion);
UseBundledNETCoreAppPackageVersionAsDefaultNetCorePatchVersion =
(parsedVersion.Patch == 0) && parsedVersion.IsPrerelease ? "true" : "false";
return true;
}
}
}

3
packaging/osx/clisdk/scripts/postinstall
View file

@ -8,9 +8,6 @@ PACKAGE=$1
INSTALL_DESTINATION=$2
INSTALL_TEMP_HOME=/tmp/dotnet-installer
# A temporary fix for the permissions issue(s)
chmod -R 755 $INSTALL_DESTINATION
first_run() {
$INSTALL_DESTINATION/dotnet exec $INSTALL_DESTINATION/sdk/%SDK_VERSION%/dotnet.dll internal-reportinstallsuccess "$1" > /dev/null 2>&1 || true
}

26
packaging/windows/clisdk/StableFileIdForApphostTransform.xslt Normal file
View file

@ -0,0 +1,26 @@
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:msxsl="urn:schemas-microsoft-com:xslt"
exclude-result-prefixes="msxsl"
xmlns:wix="http://schemas.microsoft.com/wix/2006/wi"
xmlns:my="my:my">
<xsl:output method="xml" indent="yes" />
<xsl:strip-space elements="*"/>
<xsl:template match="@*|node()">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match='wix:Wix/wix:Fragment/wix:ComponentGroup/wix:Component/wix:File[contains(@Source, "AppHostTemplate\apphost.exe")]'>
<xsl:copy>
<xsl:apply-templates select="@*"/>
<xsl:attribute name="Id">
<xsl:text>apphosttemplateapphostexe</xsl:text>
</xsl:attribute>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>

17
packaging/windows/clisdk/generatemsi.ps1
View file

@ -10,7 +10,8 @@ param(
[Parameter(Mandatory=$true)][string]$DotnetCLIDisplayVersion,
[Parameter(Mandatory=$true)][string]$DotnetCLINugetVersion,
[Parameter(Mandatory=$true)][string]$UpgradeCode,
[Parameter(Mandatory=$true)][string]$Architecture
[Parameter(Mandatory=$true)][string]$Architecture,
[Parameter(Mandatory=$true)][string]$StableFileIdForApphostTransform
)
. "$PSScriptRoot\..\..\..\scripts\common\_common.ps1"
@ -26,7 +27,19 @@ function RunHeat
Write-Output Running heat..
.\heat.exe dir `"$inputDir`" -template fragment -sreg -gg -var var.DotnetSrc -cg InstallFiles -srd -dr DOTNETHOME -out $InstallFileswsx | Out-Host
# -t $StableFileIdForApphostTransform to avoid sign check baseline apphost.exe name changes every build. Sign check uses File Id in MSI as whitelist name.
# Template apphost.exe get a new "File Id" in msi different every time (since File Id is generated according to file
# path, and file path has version number)
# use XSLT tranform to match the file path contains "AppHostTemplate\apphost.exe" and give it the same ID all the time.
.\heat.exe dir `"$inputDir`" -template fragment `
-sreg -gg `
-var var.DotnetSrc `
-cg InstallFiles `
-srd `
-dr DOTNETHOME `
-t $StableFileIdForApphostTransform `
-out $InstallFileswsx | Out-Host
if($LastExitCode -ne 0)
{

7
scripts/obtain/dotnet-install.ps1 vendored
View file

@ -522,6 +522,7 @@ else {
throw "Invalid value for `$Runtime"
}
# Check if the SDK version is already installed.
$isAssetInstalled = Is-Dotnet-Package-Installed -InstallRoot $InstallRoot -RelativePathToPackage $dotnetPackageRelativePath -SpecificVersion $SpecificVersion
if ($isAssetInstalled) {
Say "$assetName version $SpecificVersion is already installed."
@ -561,6 +562,12 @@ catch {
Say "Extracting zip from $DownloadLink"
Extract-Dotnet-Package -ZipPath $ZipPath -OutPath $InstallRoot
# Check if the SDK version is now installed; if not, fail the installation.
$isAssetInstalled = Is-Dotnet-Package-Installed -InstallRoot $InstallRoot -RelativePathToPackage $dotnetPackageRelativePath -SpecificVersion $SpecificVersion
if (!$isAssetInstalled) {
throw "$assetName version $SpecificVersion failed to install with an unknown error."
}
Remove-Item $ZipPath
Prepend-Sdk-InstallRoot-To-Path -InstallRoot $InstallRoot -BinFolderRelativePath $BinFolderRelativePath

7
scripts/obtain/dotnet-install.sh vendored
View file

@ -754,6 +754,7 @@ install_dotnet() {
return 1
fi
# Check if the SDK version is already installed.
if is_dotnet_package_installed "$install_root" "$asset_relative_path" "$specific_version"; then
say "$asset_name version $specific_version is already installed."
return 0
@ -791,6 +792,12 @@ install_dotnet() {
say "Extracting zip from $download_link"
extract_dotnet_package "$zip_path" "$install_root"
# Check if the SDK version is now installed; if not, fail the installation.
if ! is_dotnet_package_installed "$install_root" "$asset_relative_path" "$specific_version"; then
say_err "$asset_name version $specific_version failed to install with an unknown error."
return 1
fi
return 0
}

3
src/Microsoft.DotNet.Cli.Utils/LocalizableStrings.resx
View file

@ -276,4 +276,7 @@
dotnet tool install --global {1}</value>
</data>
<data name="DotnetCliHomeUsed" xml:space="preserve">
<value>Using home directory '{0}' set by the '{1}' environment variable.</value>
</data>
</root>

5
src/Microsoft.DotNet.Cli.Utils/PathUtility.cs
View file

@ -119,6 +119,11 @@ namespace Microsoft.DotNet.Tools.Common
/// </summary>
public static string GetRelativePath(string path1, string path2)
{
if (!Path.IsPathRooted(path1) || !Path.IsPathRooted(path2))
{
throw new ArgumentException("both paths need to be rooted/full path");
}
return GetRelativePath(path1, path2, Path.DirectorySeparatorChar, true);
}

1
src/Microsoft.DotNet.Cli.Utils/Properties/AssemblyInfo.cs
View file

@ -7,6 +7,7 @@ using System.Runtime.CompilerServices;
[assembly: AssemblyMetadataAttribute("Serviceable", "True")]
[assembly: InternalsVisibleTo("dotnet, PublicKey=0024000004800000940000000602000000240000525341310004000001000100f33a29044fa9d740c9b3213a93e57c84b472c84e0b8a0e1ae48e67a9f8f6de9d5f7f3d52ac23e48ac51801f1dc950abe901da34d2a9e3baadb141a17c77ef3c565dd5ee5054b91cf63bb3c6ab83f72ab3aafe93d0fc3c2348b764fafb0b1c0733de51459aeab46580384bf9d74c4e28164b7cde247f891ba07891c9d872ad2bb")]
[assembly: InternalsVisibleTo("dotnet.Tests, PublicKey=0024000004800000940000000602000000240000525341310004000001000100f33a29044fa9d740c9b3213a93e57c84b472c84e0b8a0e1ae48e67a9f8f6de9d5f7f3d52ac23e48ac51801f1dc950abe901da34d2a9e3baadb141a17c77ef3c565dd5ee5054b91cf63bb3c6ab83f72ab3aafe93d0fc3c2348b764fafb0b1c0733de51459aeab46580384bf9d74c4e28164b7cde247f891ba07891c9d872ad2bb")]
[assembly: InternalsVisibleTo("Microsoft.DotNet.Configurer, PublicKey=0024000004800000940000000602000000240000525341310004000001000100f33a29044fa9d740c9b3213a93e57c84b472c84e0b8a0e1ae48e67a9f8f6de9d5f7f3d52ac23e48ac51801f1dc950abe901da34d2a9e3baadb141a17c77ef3c565dd5ee5054b91cf63bb3c6ab83f72ab3aafe93d0fc3c2348b764fafb0b1c0733de51459aeab46580384bf9d74c4e28164b7cde247f891ba07891c9d872ad2bb")]
[assembly: InternalsVisibleTo("Microsoft.DotNet.Tools.Test, PublicKey=0024000004800000940000000602000000240000525341310004000001000100f33a29044fa9d740c9b3213a93e57c84b472c84e0b8a0e1ae48e67a9f8f6de9d5f7f3d52ac23e48ac51801f1dc950abe901da34d2a9e3baadb141a17c77ef3c565dd5ee5054b91cf63bb3c6ab83f72ab3aafe93d0fc3c2348b764fafb0b1c0733de51459aeab46580384bf9d74c4e28164b7cde247f891ba07891c9d872ad2bb")]
[assembly: InternalsVisibleTo("Microsoft.DotNet.Cli.Utils.Tests, PublicKey=0024000004800000940000000602000000240000525341310004000001000100f33a29044fa9d740c9b3213a93e57c84b472c84e0b8a0e1ae48e67a9f8f6de9d5f7f3d52ac23e48ac51801f1dc950abe901da34d2a9e3baadb141a17c77ef3c565dd5ee5054b91cf63bb3c6ab83f72ab3aafe93d0fc3c2348b764fafb0b1c0733de51459aeab46580384bf9d74c4e28164b7cde247f891ba07891c9d872ad2bb")]
[assembly: InternalsVisibleTo("Microsoft.DotNet.TestFramework, PublicKey=0024000004800000940000000602000000240000525341310004000001000100f33a29044fa9d740c9b3213a93e57c84b472c84e0b8a0e1ae48e67a9f8f6de9d5f7f3d52ac23e48ac51801f1dc950abe901da34d2a9e3baadb141a17c77ef3c565dd5ee5054b91cf63bb3c6ab83f72ab3aafe93d0fc3c2348b764fafb0b1c0733de51459aeab46580384bf9d74c4e28164b7cde247f891ba07891c9d872ad2bb")]

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.cs.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">Použije se domovský adresář {0} nastavený proměnnou prostředí {1}.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.de.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">Hiermit wird das über die Umgebungsvariable "{1}" festgelegte Basisverzeichnis "{0}" verwendet.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.es.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">Se utiliza el directorio principal "{0}" establecido por la variable de entorno "{1}".</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.fr.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">Utilisation du répertoire de base '{0}' défini par la variable d’environnement '{1}'.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.it.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">Verrà usata la home directory '{0}' impostata dalla variabile di ambiente '{1}'.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.ja.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">'{1}' 環境変数で設定したルート ディレクトリ '{0}' を使用しています。</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.ko.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet 도구를 설치하세요. install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">'{1}' 환경 변수에 의해 설정되는 홈 디렉터리 '{0}'을(를) 사용합니다.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.pl.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">Używany jest katalog główny „{0}” ustawiony za pomocą zmiennej środowiskowej „{1}”.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.pt-BR.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">Usando o diretório inicial '{0}' definido pela variável de ambiente '{1}'.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.ru.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">Используется домашний каталог "{0}", заданный переменной среды "{1}".</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.tr.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">'{1}' ortam değişkeni tarafından ayarlanan '{0}' giriş dizini kullanılıyor.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.zh-Hans.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet 工具安装 -- 全局 {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">使用由“{1}”环境变量设置的“{0}”主目录。</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

5
src/Microsoft.DotNet.Cli.Utils/xlf/LocalizableStrings.zh-Hant.xlf
View file

@ -268,6 +268,11 @@ dotnet tool install --global {1}</source>
dotnet tool install --global {1}</target>
<note />
</trans-unit>
<trans-unit id="DotnetCliHomeUsed">
<source>Using home directory '{0}' set by the '{1}' environment variable.</source>
<target state="translated">使用依 '{1}' 環境變數設定的主目錄 '{0}'。</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

2
src/Microsoft.DotNet.Configurer/AspNetCertificateSentinel.cs
View file

@ -21,7 +21,7 @@ namespace Microsoft.DotNet.Configurer
private string SentinelPath => Path.Combine(_dotnetUserProfileFolderPath, SENTINEL);
public AspNetCertificateSentinel(CliFolderPathCalculator cliFallbackFolderPathCalculator) :
public AspNetCertificateSentinel() :
this(
CliFolderPathCalculator.DotnetUserProfileFolderPath,
FileSystemWrapper.Default.File,

59
src/Microsoft.DotNet.Configurer/CliFolderPathCalculator.cs
View file

@ -4,40 +4,59 @@
using System;
using System.IO;
using System.Runtime.InteropServices;
using Microsoft.DotNet.Cli.Utils;
using NuGet.Common;
namespace Microsoft.DotNet.Configurer
{
public class CliFolderPathCalculator
public static class CliFolderPathCalculator
{
public const string DotnetHomeVariableName = "DOTNET_CLI_HOME";
private const string DotnetProfileDirectoryName = ".dotnet";
private const string ToolsShimFolderName = "tools";
public string CliFallbackFolderPath => Environment.GetEnvironmentVariable("DOTNET_CLI_TEST_FALLBACKFOLDER") ??
Path.Combine(new DirectoryInfo(AppContext.BaseDirectory).Parent.FullName, "NuGetFallbackFolder");
public string ToolsShimPath => Path.Combine(DotnetUserProfileFolderPath, ToolsShimFolderName);
public string ToolsPackagePath => ToolPackageFolderPathCalculator.GetToolPackageFolderPath(ToolsShimPath);
public BashPathUnderHomeDirectory ToolsShimPathInUnix
public static string CliFallbackFolderPath =>
Environment.GetEnvironmentVariable("DOTNET_CLI_TEST_FALLBACKFOLDER") ??
Path.Combine(new DirectoryInfo(AppContext.BaseDirectory).Parent.FullName, "NuGetFallbackFolder");
public static string ToolsShimPath => Path.Combine(DotnetUserProfileFolderPath, ToolsShimFolderName);
public static string ToolsPackagePath => ToolPackageFolderPathCalculator.GetToolPackageFolderPath(ToolsShimPath);
public static BashPathUnderHomeDirectory ToolsShimPathInUnix =>
new BashPathUnderHomeDirectory(
DotnetHomePath,
Path.Combine(DotnetProfileDirectoryName, ToolsShimFolderName));
public static string DotnetUserProfileFolderPath =>
Path.Combine(DotnetHomePath, DotnetProfileDirectoryName);
public static string PlatformHomeVariableName =>
RuntimeInformation.IsOSPlatform(OSPlatform.Windows) ? "USERPROFILE" : "HOME";
public static string DotnetHomePath
{
get
{
return new BashPathUnderHomeDirectory(Environment.GetEnvironmentVariable("HOME"),
Path.Combine(DotnetProfileDirectoryName, ToolsShimFolderName));
var home = Environment.GetEnvironmentVariable(DotnetHomeVariableName);
if (string.IsNullOrEmpty(home))
{
home = Environment.GetEnvironmentVariable(PlatformHomeVariableName);
if (string.IsNullOrEmpty(home))
{
throw new ConfigurationException(
string.Format(
LocalizableStrings.FailedToDetermineUserHomeDirectory,
DotnetHomeVariableName))
.DisplayAsError();
}
}
return home;
}
}
public static string DotnetUserProfileFolderPath
{
get
{
string profileDir = Environment.GetEnvironmentVariable(
RuntimeInformation.IsOSPlatform(OSPlatform.Windows) ? "USERPROFILE" : "HOME");
return Path.Combine(profileDir, DotnetProfileDirectoryName);
}
}
public string NuGetUserSettingsDirectory =>
public static string NuGetUserSettingsDirectory =>
NuGetEnvironment.GetFolderPath(NuGetFolderPath.UserSettingsDirectory);
}
}

22
src/Microsoft.DotNet.Configurer/ConfigurationException.cs Normal file
View file

@ -0,0 +1,22 @@
// Copyright (c) .NET Foundation and contributors. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
using System;
namespace Microsoft.DotNet.Configurer
{
internal class ConfigurationException : Exception
{
public ConfigurationException()
{
}
public ConfigurationException(string message) : base(message)
{
}
public ConfigurationException(string message, Exception innerException) : base(message, innerException)
{
}
}
}

24
src/Microsoft.DotNet.Configurer/DotnetFirstRunConfiguration.cs Normal file
View file

@ -0,0 +1,24 @@
// Copyright (c) .NET Foundation and contributors. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
namespace Microsoft.DotNet.Configurer
{
public class DotnetFirstRunConfiguration
{
public bool GenerateAspNetCertificate { get; }
public bool PrintTelemetryMessage { get; }
public bool SkipFirstRunExperience { get; }
public DotnetFirstRunConfiguration(
bool generateAspNetCertificate,
bool printTelemetryMessage,
bool skipFirstRunExperience)
{
GenerateAspNetCertificate = generateAspNetCertificate;
PrintTelemetryMessage = printTelemetryMessage;
SkipFirstRunExperience = skipFirstRunExperience;
}
}
}

21
src/Microsoft.DotNet.Configurer/DotnetFirstTimeUseConfigurer.cs
View file

@ -12,7 +12,7 @@ namespace Microsoft.DotNet.Configurer
public class DotnetFirstTimeUseConfigurer
{
private IReporter _reporter;
private IEnvironmentProvider _environmentProvider;
private DotnetFirstRunConfiguration _dotnetFirstRunConfiguration;
private INuGetCachePrimer _nugetCachePrimer;
private INuGetCacheSentinel _nugetCacheSentinel;
private IFirstTimeUseNoticeSentinel _firstTimeUseNoticeSentinel;
@ -29,7 +29,7 @@ namespace Microsoft.DotNet.Configurer
IAspNetCertificateSentinel aspNetCertificateSentinel,
IAspNetCoreCertificateGenerator aspNetCoreCertificateGenerator,
IFileSentinel toolPathSentinel,
IEnvironmentProvider environmentProvider,
DotnetFirstRunConfiguration dotnetFirstRunConfiguration,
IReporter reporter,
string cliFallbackFolderPath,
IEnvironmentPath pathAdder)
@ -40,7 +40,7 @@ namespace Microsoft.DotNet.Configurer
_aspNetCertificateSentinel = aspNetCertificateSentinel;
_aspNetCoreCertificateGenerator = aspNetCoreCertificateGenerator;
_toolPathSentinel = toolPathSentinel;
_environmentProvider = environmentProvider;
_dotnetFirstRunConfiguration = dotnetFirstRunConfiguration;
_reporter = reporter;
_cliFallbackFolderPath = cliFallbackFolderPath;
_pathAdder = pathAdder ?? throw new ArgumentNullException(nameof(pathAdder));
@ -93,11 +93,8 @@ namespace Microsoft.DotNet.Configurer
#if EXCLUDE_ASPNETCORE
return false;
#else
var generateAspNetCertificate =
_environmentProvider.GetEnvironmentVariableAsBool("DOTNET_GENERATE_ASPNET_CERTIFICATE", true);
return ShouldRunFirstRunExperience() &&
generateAspNetCertificate &&
_dotnetFirstRunConfiguration.GenerateAspNetCertificate &&
!_aspNetCertificateSentinel.Exists();
#endif
}
@ -116,11 +113,8 @@ namespace Microsoft.DotNet.Configurer
private bool ShouldPrintFirstTimeUseNotice()
{
var showFirstTimeUseNotice =
_environmentProvider.GetEnvironmentVariableAsBool("DOTNET_PRINT_TELEMETRY_MESSAGE", true);
return ShouldRunFirstRunExperience() &&
showFirstTimeUseNotice &&
_dotnetFirstRunConfiguration.PrintTelemetryMessage &&
!_firstTimeUseNoticeSentinel.Exists();
}
@ -157,10 +151,7 @@ namespace Microsoft.DotNet.Configurer
private bool ShouldRunFirstRunExperience()
{
var skipFirstTimeExperience =
_environmentProvider.GetEnvironmentVariableAsBool("DOTNET_SKIP_FIRST_TIME_EXPERIENCE", false);
return !skipFirstTimeExperience;
return !_dotnetFirstRunConfiguration.SkipFirstRunExperience;
}
}
}

2
src/Microsoft.DotNet.Configurer/FirstTimeUseNoticeSentinel.cs
View file

@ -19,7 +19,7 @@ namespace Microsoft.DotNet.Configurer
private string SentinelPath => Path.Combine(_dotnetUserProfileFolderPath, SENTINEL);
public FirstTimeUseNoticeSentinel(CliFolderPathCalculator cliFolderPathCalculator) :
public FirstTimeUseNoticeSentinel() :
this(
CliFolderPathCalculator.DotnetUserProfileFolderPath,
FileSystemWrapper.Default.File,

3
src/Microsoft.DotNet.Configurer/LocalizableStrings.resx
View file

@ -154,4 +154,7 @@ Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</value>
</data>
<data name="FailedToDetermineUserHomeDirectory" xml:space="preserve">
<value>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</value>
</data>
</root>

1
src/Microsoft.DotNet.Configurer/Microsoft.DotNet.Configurer.csproj
View file

@ -17,6 +17,7 @@
</ItemGroup>
<ItemGroup>
<PackageReference Include="NETStandard.Library" Version="2.0.0" />
<PackageReference Include="NuGet.Common" Version="$(NuGetCommonPackageVersion)" />
<PackageReference Include="NuGet.Configuration" Version="$(NuGetConfigurationPackageVersion)" />
<PackageReference Include="Microsoft.DotNet.Archive" Version="$(MicrosoftDotNetArchivePackageVersion)" />

17
src/Microsoft.DotNet.Configurer/NuGetCachePrimer.cs
View file

@ -17,31 +17,20 @@ namespace Microsoft.DotNet.Configurer
private readonly INuGetCacheSentinel _nuGetCacheSentinel;
private readonly CliFolderPathCalculator _cliFolderPathCalculator;
public NuGetCachePrimer(
INuGetPackagesArchiver nugetPackagesArchiver,
INuGetCacheSentinel nuGetCacheSentinel,
CliFolderPathCalculator cliFolderPathCalculator)
: this(nugetPackagesArchiver,
nuGetCacheSentinel,
cliFolderPathCalculator,
FileSystemWrapper.Default.File)
public NuGetCachePrimer(INuGetPackagesArchiver nugetPackagesArchiver, INuGetCacheSentinel nuGetCacheSentinel)
: this(nugetPackagesArchiver, nuGetCacheSentinel, FileSystemWrapper.Default.File)
{
}
internal NuGetCachePrimer(
INuGetPackagesArchiver nugetPackagesArchiver,
INuGetCacheSentinel nuGetCacheSentinel,
CliFolderPathCalculator cliFolderPathCalculator,
IFile file)
{
_nugetPackagesArchiver = nugetPackagesArchiver;
_nuGetCacheSentinel = nuGetCacheSentinel;
_cliFolderPathCalculator = cliFolderPathCalculator;
_file = file;
}
@ -52,7 +41,7 @@ namespace Microsoft.DotNet.Configurer
return;
}
var nuGetFallbackFolder = _cliFolderPathCalculator.CliFallbackFolderPath;
var nuGetFallbackFolder = CliFolderPathCalculator.CliFallbackFolderPath;
_nugetPackagesArchiver.ExtractArchive(nuGetFallbackFolder);

4
src/Microsoft.DotNet.Configurer/NuGetCacheSentinel.cs
View file

@ -27,8 +27,8 @@ namespace Microsoft.DotNet.Configurer
private Stream InProgressSentinel { get; set; }
public NuGetCacheSentinel(CliFolderPathCalculator cliFolderPathCalculator) :
this(cliFolderPathCalculator.CliFallbackFolderPath,
public NuGetCacheSentinel() :
this(CliFolderPathCalculator.CliFallbackFolderPath,
FileSystemWrapper.Default.File,
FileSystemWrapper.Default.Directory)
{

2
src/Microsoft.DotNet.Configurer/UserLevelCacheWriter.cs
View file

@ -14,7 +14,7 @@ namespace Microsoft.DotNet.Configurer
private readonly IDirectory _directory;
private string _dotnetUserProfileFolderPath;
public UserLevelCacheWriter(CliFolderPathCalculator cliFolderPathCalculator) :
public UserLevelCacheWriter() :
this(
CliFolderPathCalculator.DotnetUserProfileFolderPath,
FileSystemWrapper.Default.File,

9
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.cs.xlf
View file

@ -64,13 +64,18 @@ Tuto chybu můžete opravit pomocí některé z těchto možností:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
Úspěšně se podařilo nainstalovat certifikát pro vývoj ASP.NET Core HTTPS Development Certificate.
Pokud chcete certifikátu důvěřovat (platí jenom pro Windows a macOS), nainstalujte nejprve nástroj dev-certs. To uděláte tak, že spustíte dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final a potom dotnet-dev-certs https --trust.
Pokud chcete certifikátu důvěřovat, spusťte dotnet dev-certs https --trust (platí jenom pro Windows a macOS). Informace o vytvoření vztahu důvěryhodnosti na jiných platformách najdete v dokumentaci k příslušné platformě.
Další informace o konfiguraci protokolu HTTPS najdete na webu https://go.microsoft.com/fwlink/?linkid=848054.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">Nešlo určit domovský adresář uživatele. Nastavte proměnnou prostředí {0}, která určí adresář, který se má použít.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

9
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.de.xlf
View file

@ -64,13 +64,18 @@ Im Folgenden finden Sie einige Optionen, um diesen Fehler zu beheben:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
Das ASP.NET Core-HTTPS-Entwicklungszertifikat wurde erfolgreich installiert.
Um dem Zertifikat zu vertrauen (nur Windows und macOS), installieren Sie zuerst das Tool "dev-certs", indem Sie "dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final" und anschließend "dotnet-dev-certs https --trust" ausführen.
Um dem Zertifikat zu vertrauen, führen Sie "dotnet dev-certs https --trust" aus (nur Windows und macOS). Informationen zum Einrichten einer Vertrauensstellung auf anderen Plattformen finden Sie in der Dokumentation zur jeweiligen Plattform.
Weitere Informationen zur Konfiguration von HTTPS finden Sie unter https://go.microsoft.com/fwlink/?linkid=848054.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">Das Startverzeichnis des Benutzers konnte nicht ermittelt werden. Legen Sie die Umgebungsvariable "{0}" fest, um das zu verwendende Verzeichnis anzugeben.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

9
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.es.xlf
View file

@ -63,13 +63,18 @@ Estas son algunas opciones para corregir este error:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
El certificado de desarrollo HTTPS de ASP.NET Core se ha instalado correctamente.
Para confiar en el certificado (solo Windows y macOS), instale primero la herramienta dev-certs ejecutando "dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final" y, después, ejecute "dotnet-dev-certs https --trust".
Para confiar en el certificado, ejecute "dotnet dev-certs https --trust (solo Windows y macOS). Para establecer la confianza en otras plataformas, consulte la documentación específica de la plataforma.
Para obtener más información sobre la configuración HTTPS, vea https://go.microsoft.com/fwlink/?linkid=848054.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">No se puede determinar el directorio raíz del usuario. Establezca la variable de entorno “{0}” para especificar el directorio que debe usarse.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

9
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.fr.xlf
View file

@ -64,13 +64,18 @@ Voici quelques options pour corriger cette erreur :
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
Installation réussie du certificat de développement HTTPS ASP.NET Core.
Pour approuver le certificat (Windows et macOS uniquement), installez d'abord l'outil dev-certs en exécutant 'dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final', puis exécutez 'dotnet-dev-certs https --trust'.
Pour approuver le certificat, exécutez 'dotnet dev-certs https --trust' (Windows et macOS uniquement). Pour établir une relation d'approbation sur d'autres plateformes, consultez la documentation spécifique à la plateforme.
Pour plus d'informations sur la configuration du protocole HTTPS, consultez https://go.microsoft.com/fwlink/?linkid=848054.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">Impossible de déterminer le répertoire de base de l'utilisateur. Définissez la variable d'environnement '{0}' pour spécifier le répertoire à utiliser.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

11
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.it.xlf
View file

@ -64,13 +64,18 @@ Ecco alcune opzioni per correggere questo errore:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
------------
<target state="translated">ASP.NET Core
--------------
Il certificato di sviluppo HTTPS di ASP.NET Core è stato installato.
Per considerare attendibile il certificato (solo Windows e macOS), installare prima lo strumento dev-certs eseguendo 'dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final' e quindi eseguire 'dotnet-dev-certs https --trust'.
Per considerare attendibile il certificato, eseguire 'dotnet dev-certs https --trust' (solo per Windows e macOS). Per l'attendibilità su altre piattaforme, fare riferimento alla documentazione specifica della piattaforma.
Per altre informazioni sulla configurazione di HTTPS, vedere https://go.microsoft.com/fwlink/?linkid=848054.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">Non è stato possibile determinare la home directory dell'utente. Impostare la variabile di ambiente '{0}' per specificare la directory da usare.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

9
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.ja.xlf
View file

@ -64,13 +64,18 @@ Here are some options to fix this error:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
ASP.NET Core HTTPS 開発証明書が正常にインストールされました。
証明書を信頼する (Windows および macOS のみ) には、まず 'dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final' を実行して dev-certs ツールをインストールし、次に 'dotnet-dev-certs https --trust' を実行します。
証明書を信頼するには、'dotnet dev-certs https --trust' (Windows および macOS のみ) を実行します。その他のプラットフォームで信頼を確立するには、プラットフォーム固有のドキュメントをご覧ください。
HTTPS を構成する方法の詳細については、https://go.microsoft.com/fwlink/?linkid=848054 をご覧ください。</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">ユーザーのホーム ディレクトリを特定できませんでした。使用するディレクトリを指定するには、'{0}' 環境変数を設定してください。</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

9
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.ko.xlf
View file

@ -64,13 +64,18 @@ Here are some options to fix this error:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
ASP.NET Core HTTPS 개발 인증서를 설치했습니다.
인증서를 신뢰하려면(Windows 및 macOS만 해당) 먼저 'dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final'을 실행하여 dev-certs 도구를 설치한 다음, 'dotnet-dev-certs https --trust'를 실행하세요.
인증서를 신뢰하려면 'dotnet dev-certs https --trust'(Windows 및 macOS만)를 실행합니다. 다른 플랫폼에서 신뢰를 설정하는 방법에 대해서는 플랫폼별 설명서를 참조하세요.
HTTPS 구성에 대한 자세한 내용은 https://go.microsoft.com/fwlink/?linkid=848054를 참조하세요.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">사용자의 홈 디렉터리를 확인할 수 없습니다. '{0}' 환경 변수를 설정하여 사용할 디렉터리를 지정하세요.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

11
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.pl.xlf
View file

@ -64,11 +64,16 @@ Oto kilka opcji naprawiania tego błędu:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
Pomyślnie zainstalowano certyfikat deweloperski protokołu HTTPS programu ASP.NET Core.
Aby ufać temu certyfikatowi (dotyczy tylko systemów Windows i macOS), najpierw zainstaluj narzędzie dev-certs, uruchamiając polecenie „dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final”, a następnie uruchom polecenie „dotnet-dev-certs https --trust”.
Aby uzyskać więcej informacji dotyczących konfigurowania protokołu HTTPS, zobacz https://go.microsoft.com/fwlink/?linkid=848054.</target>
Aby ufać temu certyfikatowi, uruchom polecenie „dotnet dev-certs https --trust” (dotyczy tylko systemów Windows i macOS). Aby nawiązać relację zaufania na innych platformach, zapoznaj się z dokumentacją specyficzną dla danej platformy.
Aby uzyskać więcej informacji na temat konfigurowania protokołu HTTPS, zobacz https://go.microsoft.com/fwlink/?linkid=848054.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">Nie można określić katalogu macierzystego użytkownika. Ustaw zmienną środowiskową „{0}”, aby określić katalog do użycia.</target>
<note />
</trans-unit>
</body>

13
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.pt-BR.xlf
View file

@ -64,11 +64,16 @@ Aqui estão algumas opções para corrigir este erro:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
Certificado de Desenvolvimento HTTPS ASP.NET Core instalado com êxito.
Para confiar no certificado (apenas Windows e macOS), primeiramente instale a ferramenta dev-certs executando 'dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final' e, em seguida, execute 'dotnet-dev-certs https --trust'.
Para saber mais sobre a configuração de HTTPS, acesse https://go.microsoft.com/fwlink/?linkid=848054.</target>
O certificado de desenvolvimento HTTPS do ASP.NET Core foi instalado com êxito.
Para confiar no certificado, execute 'dotnet dev-certs https --trust' (somente Windows e macOS). Para estabelecer a confiança em outras plataformas, consulte a documentação específica da plataforma.
Para obter mais informações de como configurar HTTPS, confira https://go.microsoft.com/fwlink/?linkid=848054.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">O diretório inicial do usuário não pôde ser definido. Configure a variável de ambiente '{0}' para especificar o diretório a ser utilizado.</target>
<note />
</trans-unit>
</body>

9
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.ru.xlf
View file

@ -64,13 +64,18 @@ Here are some options to fix this error:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
Сертификат разработки HTTPS для ASP.NET Core установлен.
Чтобы сделать сертификат доверенным (только Windows и macOS), сначала установите инструмент dev-certs, выполнив команду "dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final", а затем выполните "dotnet-dev-certs https --trust".
Чтобы сделать сертификат доверенным, выполните команду dotnet dev-certs https --trust (только для Windows и macOS). Чтобы сделать сертификат доверенным на других платформах, обратитесь к документации по этим платформам.
Дополнительные сведения о настройке HTTPS: https://go.microsoft.com/fwlink/?linkid=848054.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">Не удалось определить домашний каталог пользователя. Чтобы указать нужный каталог, задайте переменную среды "{0}".</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

11
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.tr.xlf
View file

@ -64,11 +64,16 @@ Bu hatayı düzeltmek için bazı seçenekler:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
ASP.NET Core HTTPS Geliştirme Sertifikası başarıyla yüklendi.
Sertifikaya güvenmek için (yalnızca Windows ve macOS) önce 'dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final', sonra 'dotnet-dev-certs https --trust' komutlarını çalıştırarak dev-certs aracını yükleyin.
HTTPS yapılandırması hakkında daha fazla bilgi için bkz. https://go.microsoft.com/fwlink/?linkid=848054.</target>
Sertifikaya güvenmek için 'dotnet dev-certs https --trust' komutunu çalıştırın (yalnızca Windows ve macOS). Diğer platformlarda güven ilişkisini oluşturmak için ilgili platforma özgü belgelere başvurun.
HTTPS yapılandırması hakkında daha fazla bilgi edinmek için bkz. https://go.microsoft.com/fwlink/?linkid=848054.</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">Kullanıcının giriş dizini belirlenemedi. Kullanılacak dizini belirtmek için '{0}' ortam değişkenini ayarlayın.</target>
<note />
</trans-unit>
</body>

9
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.zh-Hans.xlf
View file

@ -64,13 +64,18 @@ Here are some options to fix this error:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
已成功安装 ASP.NET Core HTTPS 开发证书。
要信任证书(仅限 Windows 和 macOS)，请首先通过运行 "dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final" 安装 dev-certs 工具，然后运行 "dotnet-dev-certs https --trust"。
要信任证书，请运行 "dotnet dev-certs https --trust"(仅限 Windows 和 macOS)。要在其他平台上建立信任，请参阅特定于平台的文档。
有关配置 HTTPS 的详细信息，请参阅 https://go.microsoft.com/fwlink/?linkid=848054。</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">无法确定用户的主目录。设置“{0}”环境变量以指定要使用的目录。</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

11
src/Microsoft.DotNet.Configurer/xlf/LocalizableStrings.zh-Hant.xlf
View file

@ -64,11 +64,16 @@ Here are some options to fix this error:
Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.</source>
<target state="needs-review-translation">ASP.NET Core
<target state="translated">ASP.NET Core
------------
已成功安裝 ASP.NET Core HTTPS 開發憑證。
若要信任此憑證 (僅限 Windows 與 macOS)，請先執行 'dotnet tool install dotnet-dev-certs -g --version 2.1.0-preview1-final' 來安裝 dev-certs 工具，然後再執行 'dotnet-dev-certs https --trust'。
如需如何設定 HTTPS 的詳細資訊，請參閱 https://go.microsoft.com/fwlink/?linkid=848054。</target>
若要信任此憑證，請執行 'dotnet dev-certs https --trust' (僅限 Windows 與 macOS)。若要在其他平台上建立信任，請參閱各平台適用的文件。
如需設定 HTTPS 的詳細資訊，請參閱 https://go.microsoft.com/fwlink/?linkid=848054。</target>
<note />
</trans-unit>
<trans-unit id="FailedToDetermineUserHomeDirectory">
<source>The user's home directory could not be determined. Set the '{0}' environment variable to specify the directory to use.</source>
<target state="translated">無法判定該使用者的主目錄。請設定 '{0}' 環境變數，指定要使用的目錄。</target>
<note />
</trans-unit>
</body>

11
src/Microsoft.DotNet.InternalAbstractions/DirectoryPath.cs
View file

@ -10,8 +10,17 @@ namespace Microsoft.Extensions.EnvironmentAbstractions
{
public string Value { get; }
/// <summary>
/// Create DirectoryPath to repesent a absolute directory path. Note it may not exist.
/// </summary>
/// <param name="value">If the value is not rooted. Path.GetFullPath will be called during the consturctor.</param>
public DirectoryPath(string value)
{
if (!Path.IsPathRooted(value))
{
value = Path.GetFullPath(value);
}
Value = value;
}
@ -46,7 +55,7 @@ namespace Microsoft.Extensions.EnvironmentAbstractions
public DirectoryPath GetParentPath()
{
return new DirectoryPath(Directory.GetParent(Path.GetFullPath(Value)).FullName);
return new DirectoryPath(Path.GetDirectoryName(Value));
}
}
}

9
src/Microsoft.DotNet.InternalAbstractions/FilePath.cs
View file

@ -9,8 +9,17 @@ namespace Microsoft.Extensions.EnvironmentAbstractions
{
public string Value { get; }
/// <summary>
/// Create FilePath to repesent a absolute file path. Note it may not exist.
/// </summary>
/// <param name="value">If the value is not rooted. Path.GetFullPath will be called during the consturctor.</param>
public FilePath(string value)
{
if (!Path.IsPathRooted(value))
{
value = Path.GetFullPath(value);
}
Value = value;
}

2
src/dotnet/BuildServer/xlf/LocalizableStrings.cs.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">Nepodařilo se přečíst soubor s identifikátorem PID {0}: {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.de.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">Fehler beim Lesen der PID-Datei "{0}": {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.es.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">No se pudo leer el archivo pid "{0}": {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.fr.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">Échec de lecture du fichier pid '{0}' : {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.it.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">Non è stato possibile leggere il file '{0}' del PID: {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.ja.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">pid ファイル '{0}' の読み取りに失敗しました: {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.ko.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">pid 파일 '{0}'을(를) 읽지 못했습니다. {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.pl.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">Nie można odczytać pliku pid „{0}”: {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.pt-BR.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">Falha ao ler o arquivo PID '{0}': {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.ru.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">Не удалось считать файл идентификатора процесса "{0}": {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.tr.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">'{0}' adlı pid dosyası okunamadı: {1}</target>
<note />
</trans-unit>
</body>

2
src/dotnet/BuildServer/xlf/LocalizableStrings.zh-Hans.xlf
View file

@ -24,7 +24,7 @@
</trans-unit>
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<target state="translated">未能读取 pid 文件“{0}”: {1}</target>
<note />
</trans-unit>
</body>

Some files were not shown because too many files have changed in this diff Show more