Add verbosity option to install tool command.

This commit adds the `--verbosity` option to the `install tool` command.

MSBuild/NuGet output is now controllable by the user and defaults to being "quiet".

This enables users to see warnings from NuGet that otherwise would be swallowed
unless NuGet returned a non-zero exit code. As a byproduct of this change, the
exception handling and error messages related to obtaining tool packages was
retooled. We no longer display `install tool` command line help for installation
failures, as it should only be displayed for command line syntax errors.

Fixes #8465.
This commit is contained in:
Peter Huene 2018-01-17 19:26:52 -08:00
parent 085452eaae
commit 7ebfdde749
No known key found for this signature in database
GPG key ID: E1D265D820213D6A
50 changed files with 1068 additions and 1103 deletions

View file

@ -674,40 +674,6 @@
<target state="translated">Se ha quitado el proyecto "{0}" de la solución.</target>
<note />
</trans-unit>
<trans-unit id="CannotBeNullOrWhitespace">
<source>Cannot be null or whitespace.</source>
<target state="new">Cannot be null or whitespace.</target>
<note />
</trans-unit>
<trans-unit id="ContainInvalidCharacters">
<source>Contains one or more invalid characters: {0}</source>
<target state="new">Contains one or more invalid characters: {0}</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsInvalidXml">
<source>The tool's settings file is invalid xml.
{0}</source>
<target state="new">The tool's settings file is invalid xml.
{0}</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingInvalidRunner">
<source>The tool's settings file has non "dotnet" as runner.</source>
<target state="new">The tool's settings file has non "dotnet" as runner.</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingMoreThanOneCommand">
<source>The tool's settings file has more than one command defined.</source>
<target state="new">The tool's settings file has more than one command defined.</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsContainError">
<source>The tool's settings file contains error.
{0}</source>
<target state="new">The tool's settings file contains error.
{0}</target>
<note />
</trans-unit>
<trans-unit id="NuGetConfigurationFileDoesNotExist">
<source>NuGet configuration file {0} does not exist.</source>
<target state="new">NuGet configuration file {0} does not exist.</target>
@ -797,6 +763,36 @@ setx PATH "%PATH%;{1}"</target>
<target state="new">Package '{0}' is missing tool settings file DotnetToolSettings.xml.</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsInvalidXml">
<source>Invalid XML: {0}</source>
<target state="new">Invalid XML: {0}</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsMissingCommandName">
<source>Tool defines a command with a missing name setting.</source>
<target state="new">Tool defines a command with a missing name setting.</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsMissingEntryPoint">
<source>Command '{0}' is missing an entry point setting.</source>
<target state="new">Command '{0}' is missing an entry point setting.</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsInvalidCommandName">
<source>Command '{0}' contains one or more of the following invalid characters: {1}.</source>
<target state="new">Command '{0}' contains one or more of the following invalid characters: {1}.</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsMoreThanOneCommand">
<source>More than one command is defined for the tool.</source>
<target state="new">More than one command is defined for the tool.</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsUnsupportedRunner">
<source>Command '{0}' uses unsupported runner '{1}'."</source>
<target state="new">Command '{0}' uses unsupported runner '{1}'."</target>
<note />
</trans-unit>
</body>
</file>
</xliff>