Localization for tools work so far (#8251)

This commit is contained in:
William Lee 2018-01-13 09:40:48 -08:00 committed by GitHub
parent 2cfc65a0c4
commit e8f7ddd01b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
60 changed files with 2848 additions and 83 deletions

View file

@ -520,4 +520,68 @@
<data name="NoRestoreDescription" xml:space="preserve">
<value>Does not do an implicit restore when executing the command.</value>
</data>
<data name="CannotBeNullOrWhitespace" xml:space="preserve">
<value>Cannot be null or whitespace.</value>
</data>
<data name="ContainInvalidCharacters" xml:space="preserve">
<value>Contains one or more invalid characters: {0}</value>
</data>
<data name="NuGetConfigurationFileDoesNotExist" xml:space="preserve">
<value>NuGet configuration file {0} does not exist.</value>
</data>
<data name="ToolSettingInvalidRunner" xml:space="preserve">
<value>The tool's settings file has non "dotnet" as runner.</value>
</data>
<data name="ToolSettingMoreThanOneCommand" xml:space="preserve">
<value>The tool's settings file has more than one command defined.</value>
</data>
<data name="ToolSettingsContainError" xml:space="preserve">
<value>The tool's settings file contains error.
{0}</value>
</data>
<data name="ToolSettingsInvalidXml" xml:space="preserve">
<value>The tool's settings file is invalid xml.
{0}</value>
</data>
<data name="EnvironmentPathLinuxManualInstruction" xml:space="preserve">
<value>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</value>
</data>
<data name="EnvironmentPathLinuxNeedLogout" xml:space="preserve">
<value>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</value>
</data>
<data name="EnvironmentPathOSXManualInstruction" xml:space="preserve">
<value>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</value>
</data>
<data name="EnvironmentPathOSXNeedReopen" xml:space="preserve">
<value>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</value>
</data>
<data name="EnvironmentPathWindowsManualInstruction" xml:space="preserve">
<value>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</value>
</data>
<data name="EnvironmentPathWindowsNeedReopen" xml:space="preserve">
<value>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</value>
</data>
<data name="FailInstallToolPermission" xml:space="preserve">
<value>Failed to change permission:
Error: {0}
Output: {1}</value>
</data>
<data name="FailInstallToolSameName" xml:space="preserve">
<value>Failed to install tool {0}. A command with the same name already exists.</value>
</data>
</root>

View file

@ -5,6 +5,7 @@ using System;
using System.Linq;
using Microsoft.DotNet.Cli.Utils;
using Microsoft.DotNet.Configurer;
using Microsoft.DotNet.Tools;
using Microsoft.Extensions.EnvironmentAbstractions;
namespace Microsoft.DotNet.ShellShim
@ -67,18 +68,15 @@ namespace Microsoft.DotNet.ShellShim
if (_fileSystem.Exists(_profiledDotnetCliToolsPath))
{
_reporter.WriteLine(
"Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.");
CommonLocalizableStrings.EnvironmentPathLinuxNeedLogout);
}
else
{
// similar to https://code.visualstudio.com/docs/setup/mac
_reporter.WriteLine(
$"Cannot find the tools executable path. Please ensure {_packageExecutablePath.Path} is added to your PATH.{Environment.NewLine}" +
$"If you are using bash. You can do this by running the following command:{Environment.NewLine}{Environment.NewLine}" +
$"cat << EOF >> ~/.bash_profile{Environment.NewLine}" +
$"# Add .NET Core SDK tools{Environment.NewLine}" +
$"export PATH=\"$PATH:{_packageExecutablePath.Path}\"{Environment.NewLine}" +
$"EOF");
string.Format(
CommonLocalizableStrings.EnvironmentPathLinuxManualInstruction,
_packageExecutablePath.Path, _packageExecutablePath.Path));
}
}
}

View file

@ -5,6 +5,7 @@ using System;
using System.Linq;
using Microsoft.DotNet.Cli.Utils;
using Microsoft.DotNet.Configurer;
using Microsoft.DotNet.Tools;
using Microsoft.Extensions.EnvironmentAbstractions;
namespace Microsoft.DotNet.ShellShim
@ -67,18 +68,15 @@ namespace Microsoft.DotNet.ShellShim
if (_fileSystem.Exists(PathDDotnetCliToolsPath))
{
_reporter.WriteLine(
"Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.");
CommonLocalizableStrings.EnvironmentPathOSXNeedReopen);
}
else
{
// similar to https://code.visualstudio.com/docs/setup/mac
_reporter.WriteLine(
$"Cannot find the tools executable path. Please ensure {_packageExecutablePath.Path} is added to your PATH.{Environment.NewLine}" +
$"If you are using bash, You can do this by running the following command:{Environment.NewLine}{Environment.NewLine}" +
$"cat << EOF >> ~/.bash_profile{Environment.NewLine}" +
$"# Add .NET Core SDK tools{Environment.NewLine}" +
$"export PATH=\"$PATH:{_packageExecutablePath.Path}\"{Environment.NewLine}" +
$"EOF");
string.Format(
CommonLocalizableStrings.EnvironmentPathOSXManualInstruction,
_packageExecutablePath.Path, _packageExecutablePath.Path));
}
}
}

View file

@ -6,6 +6,7 @@ using System.IO;
using System.Runtime.InteropServices;
using System.Text;
using Microsoft.DotNet.Cli.Utils;
using Microsoft.DotNet.Tools;
using Microsoft.Extensions.EnvironmentAbstractions;
namespace Microsoft.DotNet.ShellShim
@ -47,7 +48,8 @@ namespace Microsoft.DotNet.ShellShim
if (File.Exists(Path.Combine(_pathToPlaceShim, shellCommandName)))
{
throw new GracefulException(
$"Failed to install tool {shellCommandName}. A command with the same name already exists.");
string.Format(CommonLocalizableStrings.FailInstallToolSameName,
shellCommandName));
}
}
@ -80,9 +82,8 @@ namespace Microsoft.DotNet.ShellShim
if (result.ExitCode != 0)
{
throw new GracefulException(
"Failed to change permission:" +
$"{Environment.NewLine}Error: " + result.StdErr +
$"{Environment.NewLine}Output: " + result.StdOut);
string.Format(CommonLocalizableStrings.FailInstallToolPermission, result.StdErr,
result.StdOut));
}
}
}

View file

@ -4,6 +4,7 @@
using System;
using System.Linq;
using Microsoft.DotNet.Cli.Utils;
using Microsoft.DotNet.Tools;
using Microsoft.Extensions.EnvironmentAbstractions;
namespace Microsoft.DotNet.ShellShim
@ -63,14 +64,14 @@ namespace Microsoft.DotNet.ShellShim
.Contains(_packageExecutablePath))
{
_reporter.WriteLine(
"Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.");
CommonLocalizableStrings.EnvironmentPathWindowsNeedReopen);
}
else
{
_reporter.WriteLine(
$"Cannot find the tools executable path. Please ensure {_packageExecutablePath} is added to your PATH.{Environment.NewLine}" +
$"You can do this by running the following command:{Environment.NewLine}{Environment.NewLine}" +
$"setx PATH \"%PATH%;{_packageExecutablePath}\"{Environment.NewLine}");
string.Format(
CommonLocalizableStrings.EnvironmentPathWindowsManualInstruction,
_packageExecutablePath, _packageExecutablePath));
}
}
}

View file

@ -3,6 +3,7 @@
using System;
using System.IO;
using Microsoft.DotNet.Tools;
namespace Microsoft.DotNet.ToolPackage
{
@ -14,14 +15,14 @@ namespace Microsoft.DotNet.ToolPackage
{
if (string.IsNullOrWhiteSpace(commandName))
{
throw new ArgumentNullException(nameof(commandName), "Cannot be null or whitespace");
throw new ArgumentNullException(nameof(commandName), CommonLocalizableStrings.CannotBeNullOrWhitespace);
}
EnsureNoInvalidFilenameCharacters(commandName, nameof(toolAssemblyEntryPoint));
if (string.IsNullOrWhiteSpace(toolAssemblyEntryPoint))
{
throw new ArgumentNullException(nameof(toolAssemblyEntryPoint), "Cannot be null or whitespace");
throw new ArgumentNullException(nameof(toolAssemblyEntryPoint), CommonLocalizableStrings.CannotBeNullOrWhitespace);
}
CommandName = commandName;
@ -35,7 +36,8 @@ namespace Microsoft.DotNet.ToolPackage
{
throw new ArgumentException(
paramName: nameof(nameOfParam),
message: "Contains one or more invalid characters: " + new string(invalidCharactors));
message: string.Format(CommonLocalizableStrings.ContainInvalidCharacters,
new string(invalidCharactors)));
}
}

View file

@ -6,6 +6,7 @@ using System.IO;
using System.Xml;
using System.Xml.Serialization;
using Microsoft.DotNet.ToolPackage.ToolConfigurationDeserialization;
using Microsoft.DotNet.Tools;
namespace Microsoft.DotNet.ToolPackage
{
@ -28,21 +29,20 @@ namespace Microsoft.DotNet.ToolPackage
catch (InvalidOperationException e) when (e.InnerException is XmlException)
{
throw new ToolConfigurationException(
$"The tool's settings file is invalid xml. {Environment.NewLine}" +
e.InnerException.Message);
string.Format(CommonLocalizableStrings.ToolSettingsInvalidXml, e.InnerException.Message));
}
}
if (dotNetCliTool.Commands.Length != 1)
{
throw new ToolConfigurationException(
"The tool's settings file has more than one command defined.");
CommonLocalizableStrings.ToolSettingMoreThanOneCommand);
}
if (dotNetCliTool.Commands[0].Runner != "dotnet")
{
throw new ToolConfigurationException(
"The tool's settings file has non \"dotnet\" as runner.");
CommonLocalizableStrings.ToolSettingInvalidRunner);
}
var commandName = dotNetCliTool.Commands[0].Name;
@ -54,7 +54,9 @@ namespace Microsoft.DotNet.ToolPackage
}
catch (ArgumentException e)
{
throw new ToolConfigurationException($"The tool's settings file contains error {Environment.NewLine}" + e.Message);
throw new ToolConfigurationException(
string.Format(CommonLocalizableStrings.ToolSettingsContainError,
e.Message));
}
}
}

View file

@ -3,6 +3,7 @@ using System.Diagnostics;
using System.IO;
using System.Linq;
using System.Xml.Linq;
using Microsoft.DotNet.Tools;
using Microsoft.Extensions.EnvironmentAbstractions;
namespace Microsoft.DotNet.ToolPackage
@ -47,7 +48,9 @@ namespace Microsoft.DotNet.ToolPackage
{
if (!File.Exists(nugetconfig.Value.Value))
{
throw new PackageObtainException($"NuGet configuration file {Path.GetFullPath(nugetconfig.Value.Value)} does not exist.");
throw new PackageObtainException(
string.Format(CommonLocalizableStrings.NuGetConfigurationFileDoesNotExist,
Path.GetFullPath(nugetconfig.Value.Value)));
}
}

View file

@ -28,6 +28,7 @@ path-to-application:
msbuild {LocalizableStrings.MsBuildDefinition}
vstest {LocalizableStrings.VsTestDefinition}
store {LocalizableStrings.StoreDefinition}
install {LocalizableStrings.InstallDefinition}
help {LocalizableStrings.HelpDefinition}
{LocalizableStrings.CommonOptions}:

View file

@ -267,4 +267,7 @@
<data name="AdditionalDeps" xml:space="preserve">
<value>Path to additional deps.json file.</value>
</data>
</root>
<data name="InstallDefinition" xml:space="preserve">
<value>Add item to development environment.</value>
</data>
</root>

View file

@ -252,6 +252,11 @@
<target state="translated">Ukládá zadaná nastavení do úložiště runtime.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">Speichert die angegebenen Assemblys im Laufzeitspeicher.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">Almacena los ensamblados especificados en el almacén del tiempo de ejecución.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">Stocke les assemblys spécifiés dans le magasin de runtimes.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">Memorizza gli assembly specificati nell'archivio di runtime.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">指定されたアセンブリを実行時ストアに格納します。</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">지정된 어셈블리를 런타임 저장소에 저장합니다.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">Przechowuje określone zestawy w magazynie środowiska uruchomieniowego.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">Armazena os assemblies especificados no repositório de tempo de execução.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">Он сохраняет указанные сборки в хранилище среды выполнения.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">Belirtilen bütünleştirilmiş kodları çalışma zamanı deposunda depolar.</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">在运行时存储中存储指定的程序集。</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -252,6 +252,11 @@
<target state="translated">將指定組件儲存到執行階段存放區中。</target>
<note />
</trans-unit>
<trans-unit id="InstallDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -8,13 +8,14 @@ using Microsoft.DotNet.Cli.CommandLine;
using Microsoft.DotNet.Cli.Utils;
using Microsoft.DotNet.Tools.Add;
using Microsoft.DotNet.Tools.Install.Tool;
using LocalizableStrings = Microsoft.DotNet.Tools.Install.LocalizableStrings;
namespace Microsoft.DotNet.Tools.Install
{
public class InstallCommand : DotNetTopLevelCommandBase
{
protected override string CommandName => "install";
protected override string FullCommandNameLocalized => "NetInstallCommand";
protected override string FullCommandNameLocalized => LocalizableStrings.InstallFullCommandNameLocalized;
protected override string ArgumentName => Constants.ProjectArgumentName;
protected override string ArgumentDescriptionLocalized => CommonLocalizableStrings.ArgumentsProjectDescription;

View file

@ -2,6 +2,7 @@
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
using Microsoft.DotNet.Cli.CommandLine;
using LocalizableStrings = Microsoft.DotNet.Tools.Install.LocalizableStrings;
namespace Microsoft.DotNet.Cli
{
@ -10,7 +11,7 @@ namespace Microsoft.DotNet.Cli
public static Command Install()
{
return Create.Command(
"install", "",
"install", LocalizableStrings.InstallCommandDefinition,
Accept.NoArguments(),
CommonOptions.HelpOption(),
InstallToolCommandParser.InstallTool());

View file

@ -123,4 +123,53 @@
<data name="SourceOptionName" xml:space="preserve">
<value>SOURCE</value>
</data>
<data name="FailedToAddPackage" xml:space="preserve">
<value>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</value>
</data>
<data name="FailedToRestorePackage" xml:space="preserve">
<value>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</value>
</data>
<data name="InstallationSucceeded" xml:space="preserve">
<value>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</value>
</data>
<data name="InstallCommandDefinition" xml:space="preserve">
<value>Add item to development environment.</value>
</data>
<data name="InstallFailedNuget" xml:space="preserve">
<value>Install failed. Failed to download package:
NuGet returned:
{0}</value>
</data>
<data name="InstallFailedPackage" xml:space="preserve">
<value>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</value>
</data>
<data name="InstallFullCommandNameLocalized" xml:space="preserve">
<value>NetInstallCommand</value>
</data>
<data name="InstallToolCommandDefinition" xml:space="preserve">
<value>Install tool for use on the command line.</value>
</data>
<data name="InstallToolConfigfileDefinition" xml:space="preserve">
<value>NuGet configuration file</value>
</data>
<data name="InstallToolFrameworkDefinition" xml:space="preserve">
<value>Target framework to publish for. The target framework has to be specified in the project file.</value>
</data>
<data name="InstallToolPackageIdDefinition" xml:space="preserve">
<value>Package Id in NuGet</value>
</data>
<data name="InstallToolVersionDefinition" xml:space="preserve">
<value>Version of the package in NuGet</value>
</data>
</root>

View file

@ -65,7 +65,7 @@ namespace Microsoft.DotNet.Tools.Install.Tool
.PrintAddPathInstructionIfPathDoesNotExist();
Reporter.Output.WriteLine(
$"{Environment.NewLine}The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {commandName}");
string.Format(LocalizableStrings.InstallationSucceeded, commandName));
return 0;
}
@ -100,20 +100,17 @@ namespace Microsoft.DotNet.Tools.Install.Tool
{
throw new GracefulException(
message:
$"Install failed. Failed to download package:{Environment.NewLine}" +
$"NuGet returned:{Environment.NewLine}" +
$"{Environment.NewLine}" +
$"{ex.Message}",
string.Format(LocalizableStrings.InstallFailedNuget,
ex.Message),
innerException: ex);
}
catch (ToolConfigurationException ex)
{
throw new GracefulException(
message:
$"Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.{Environment.NewLine}" +
$"The error was:{Environment.NewLine}" +
$"{Environment.NewLine}" +
$"{ex.Message}",
string.Format(
LocalizableStrings.InstallFailedPackage,
ex.Message),
innerException: ex);
}
}

View file

@ -1,9 +1,7 @@
// 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.Linq;
using Microsoft.DotNet.Cli.CommandLine;
using Microsoft.DotNet.Tools.Install.Tool;
using LocalizableStrings = Microsoft.DotNet.Tools.Install.LocalizableStrings;
namespace Microsoft.DotNet.Cli
@ -13,17 +11,17 @@ namespace Microsoft.DotNet.Cli
public static Command InstallTool()
{
return Create.Command("tool",
"Install tool",
LocalizableStrings.InstallToolCommandDefinition,
Accept.ExactlyOneArgument(o => "packageId")
.With(name: "packageId",
description: "Package Id in NuGet"),
description: LocalizableStrings.InstallToolPackageIdDefinition),
Create.Option(
"--version",
"Version of the package in NuGet",
LocalizableStrings.InstallToolVersionDefinition,
Accept.ExactlyOneArgument()),
Create.Option(
"--configfile",
"NuGet configuration file",
LocalizableStrings.InstallToolConfigfileDefinition,
Accept.ExactlyOneArgument()),
Create.Option(
"--source",
@ -32,7 +30,7 @@ namespace Microsoft.DotNet.Cli
.With(name: LocalizableStrings.SourceOptionName)),
Create.Option(
"-f|--framework",
"Target framework to publish for. The target framework has to be specified in the project file.",
LocalizableStrings.InstallToolFrameworkDefinition,
Accept.ExactlyOneArgument()),
CommonOptions.HelpOption());
}

View file

@ -5,7 +5,9 @@ using System;
using System.Collections.Generic;
using Microsoft.DotNet.Cli;
using Microsoft.DotNet.ToolPackage;
using Microsoft.DotNet.Tools;
using Microsoft.Extensions.EnvironmentAbstractions;
using LocalizableStrings = Microsoft.DotNet.Tools.Install.LocalizableStrings;
namespace Microsoft.DotNet.Tools.Install.Tool
{
@ -36,13 +38,10 @@ namespace Microsoft.DotNet.Tools.Install.Tool
var result = command.Execute();
if (result.ExitCode != 0)
{
throw new PackageObtainException("Failed to add package. " +
$"{Environment.NewLine}WorkingDirectory: " +
result.StartInfo.WorkingDirectory +
$"{Environment.NewLine}Arguments: " +
result.StartInfo.Arguments +
$"{Environment.NewLine}Output: " +
result.StdErr + result.StdOut);
throw new PackageObtainException(
string.Format(
LocalizableStrings.FailedToAddPackage,
result.StartInfo.WorkingDirectory, result.StartInfo.Arguments, result.StdErr, result.StdOut));
}
}
}

View file

@ -5,9 +5,11 @@ using System;
using System.Collections.Generic;
using Microsoft.DotNet.Cli;
using Microsoft.DotNet.Cli.Utils;
using Microsoft.DotNet.Tools;
using Microsoft.DotNet.ToolPackage;
using Microsoft.DotNet.PlatformAbstractions;
using Microsoft.Extensions.EnvironmentAbstractions;
using LocalizableStrings = Microsoft.DotNet.Tools.Install.LocalizableStrings;
namespace Microsoft.DotNet.Tools.Install.Tool
{
@ -49,13 +51,10 @@ namespace Microsoft.DotNet.Tools.Install.Tool
var result = command.Execute();
if (result.ExitCode != 0)
{
throw new PackageObtainException("Failed to restore package. " +
$"{Environment.NewLine}WorkingDirectory: " +
result.StartInfo.WorkingDirectory +
$"{Environment.NewLine}Arguments: " +
result.StartInfo.Arguments +
$"{Environment.NewLine}Output: " +
result.StdErr + result.StdOut);
throw new PackageObtainException(
string.Format(
LocalizableStrings.FailedToRestorePackage,
result.StartInfo.WorkingDirectory, result.StartInfo.Arguments, result.StdErr, result.StdOut));
}
}
}

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -12,6 +12,92 @@
<target state="new">SOURCE</target>
<note />
</trans-unit>
<trans-unit id="InstallationSucceeded">
<source>
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</source>
<target state="new">
The installation succeeded. If there is no other instruction. You can type the following command in shell directly to invoke: {0}</target>
<note />
</trans-unit>
<trans-unit id="InstallCommandDefinition">
<source>Add item to development environment.</source>
<target state="new">Add item to development environment.</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedNuget">
<source>Install failed. Failed to download package:
NuGet returned:
{0}</source>
<target state="new">Install failed. Failed to download package:
NuGet returned:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFailedPackage">
<source>Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</source>
<target state="new">Install failed. The settings file in the tool's NuGet package is not valid. Please contact the owner of the NuGet package.
The error was:
{0}</target>
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>NetInstallCommand</source>
<target state="new">NetInstallCommand</target>
<note />
</trans-unit>
<trans-unit id="InstallToolCommandDefinition">
<source>Install tool for use on the command line.</source>
<target state="new">Install tool for use on the command line.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolConfigfileDefinition">
<source>NuGet configuration file</source>
<target state="new">NuGet configuration file</target>
<note />
</trans-unit>
<trans-unit id="InstallToolFrameworkDefinition">
<source>Target framework to publish for. The target framework has to be specified in the project file.</source>
<target state="new">Target framework to publish for. The target framework has to be specified in the project file.</target>
<note />
</trans-unit>
<trans-unit id="InstallToolPackageIdDefinition">
<source>Package Id in NuGet</source>
<target state="new">Package Id in NuGet</target>
<note />
</trans-unit>
<trans-unit id="InstallToolVersionDefinition">
<source>Version of the package in NuGet</source>
<target state="new">Version of the package in NuGet</target>
<note />
</trans-unit>
<trans-unit id="FailedToAddPackage">
<source>Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to add package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRestorePackage">
<source>Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</source>
<target state="new">Failed to restore package.
WorkingDirectory: {0}
Arguments: {1}
Output: {2}{3}</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">Projekt {0} byl z řešení odebrá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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">Das Projekt "{0}" wurde aus der Projektmappe entfernt.</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">Projet '{0}' retiré de la solution.</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">Il progetto `{0}` è stato rimosso dalla soluzione.</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">プロジェクト `{0}` がソリューションから削除されました。</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">'{0}' 프로젝트가 솔루션에서 제거되었습니다.</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">Projekt „{0}” został skasowany z rozwiązania.</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">O projeto `{0}` foi removido da solução.</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">Проект "{0}" удален из решения.</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">`{0}` projesi çözümden kaldırıldı.</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">已从解决方案中移除项目“{0}”。</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -674,6 +674,119 @@
<target state="translated">專案 `{0}` 已從解決方案移除。</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>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="new">Failed to change permission:
Error: {0}
Output: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
</body>
</file>
</xliff>

View file

@ -7,6 +7,7 @@ using System.Diagnostics;
using System.Runtime.InteropServices;
using FluentAssertions;
using Microsoft.DotNet.Configurer;
using Microsoft.DotNet.Tools;
using Microsoft.DotNet.Tools.Test.Utilities;
using Microsoft.Extensions.DependencyModel.Tests;
using Xunit;
@ -33,12 +34,9 @@ namespace Microsoft.DotNet.ShellShim.Tests
// similar to https://code.visualstudio.com/docs/setup/mac
fakeReporter.Message.Should().Be(
$"Cannot find the tools executable path. Please ensure /myhome/executable/path is added to your PATH.{Environment.NewLine}" +
$"If you are using bash. You can do this by running the following command:{Environment.NewLine}{Environment.NewLine}" +
$"cat << EOF >> ~/.bash_profile{Environment.NewLine}" +
$"# Add .NET Core SDK tools{Environment.NewLine}" +
$"export PATH=\"$PATH:/myhome/executable/path\"{Environment.NewLine}" +
$"EOF");
string.Format(
CommonLocalizableStrings.EnvironmentPathLinuxManualInstruction,
"/myhome/executable/path", "/myhome/executable/path"));
}
[Fact]
@ -78,8 +76,7 @@ namespace Microsoft.DotNet.ShellShim.Tests
linuxEnvironmentPath.PrintAddPathInstructionIfPathDoesNotExist();
fakeReporter.Message.Should()
.Be(
"Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.");
.Be(CommonLocalizableStrings.EnvironmentPathLinuxNeedLogout);
}
}
}

View file

@ -7,6 +7,7 @@ using System.Diagnostics;
using System.Runtime.InteropServices;
using FluentAssertions;
using Microsoft.DotNet.Configurer;
using Microsoft.DotNet.Tools;
using Microsoft.DotNet.Tools.Test.Utilities;
using Microsoft.Extensions.DependencyModel.Tests;
using Xunit;
@ -33,12 +34,9 @@ namespace Microsoft.DotNet.ShellShim.Tests
// similar to https://code.visualstudio.com/docs/setup/mac
fakeReporter.Message.Should().Be(
$"Cannot find the tools executable path. Please ensure /myhome/executable/path is added to your PATH.{Environment.NewLine}" +
$"If you are using bash, You can do this by running the following command:{Environment.NewLine}{Environment.NewLine}" +
$"cat << EOF >> ~/.bash_profile{Environment.NewLine}" +
$"# Add .NET Core SDK tools{Environment.NewLine}" +
$"export PATH=\"$PATH:/myhome/executable/path\"{Environment.NewLine}" +
$"EOF");
string.Format(
CommonLocalizableStrings.EnvironmentPathOSXManualInstruction,
"/myhome/executable/path", "/myhome/executable/path"));
}
[Theory]
@ -79,8 +77,7 @@ namespace Microsoft.DotNet.ShellShim.Tests
osxEnvironmentPath.PrintAddPathInstructionIfPathDoesNotExist();
fakeReporter.Message.Should().Be(
"Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.");
fakeReporter.Message.Should().Be(CommonLocalizableStrings.EnvironmentPathOSXNeedReopen);
}
}
}

View file

@ -6,6 +6,7 @@ using System.Collections.Generic;
using System.IO;
using System.Linq;
using FluentAssertions;
using Microsoft.DotNet.Tools;
using NuGet.Protocol.Core.Types;
using Xunit;
@ -28,7 +29,7 @@ namespace Microsoft.DotNet.ToolPackage.Tests
Action a = () => ToolConfigurationDeserializer.Deserialize("DotnetToolSettingsMalformed.xml");
a.ShouldThrow<ToolConfigurationException>()
.And.Message.Should()
.Contain("The tool's settings file is invalid xml");
.Contain(string.Format(CommonLocalizableStrings.ToolSettingsInvalidXml, string.Empty));
}
[Fact]
@ -37,7 +38,7 @@ namespace Microsoft.DotNet.ToolPackage.Tests
Action a = () => ToolConfigurationDeserializer.Deserialize("DotnetToolSettingsMissing.xml");
a.ShouldThrow<ToolConfigurationException>()
.And.Message.Should()
.Contain("The tool's settings file contains error");
.Contain(string.Format(CommonLocalizableStrings.ToolSettingsContainError, string.Empty));
}
[Fact]
@ -46,7 +47,7 @@ namespace Microsoft.DotNet.ToolPackage.Tests
Action a = () => new ToolConfiguration("na\0me", "my.dll");
a.ShouldThrow<ArgumentException>()
.And.Message.Should()
.Contain("Contains one or more invalid characters");
.Contain(string.Format(CommonLocalizableStrings.ContainInvalidCharacters, string.Empty));
}
}
}

View file

@ -39,6 +39,7 @@ SDK commands:
msbuild Runs Microsoft Build Engine (MSBuild).
vstest Runs Microsoft Test Execution Command Line Tool.
store Stores the specified assemblies in the runtime store.
install Add item to development environment.
help Show help.
Common options: