mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1
dotnet-installer/src/dotnet/BuildServer/xlf/LocalizableStrings.cs.xlf

32 lines
1.3 KiB
Text
Raw Normal View History

Implement `buildserver shutdown` command. This commit implements the `buildserver shutdown` command that can be used to shutdown MSBuild, VB/C# compiler, and Razor build servers. By default, all three build servers are shut down. Options can be passed to shut down a subset of the build servers. Fixes #8185.
2018-03-27 20:26:55 -07:00
<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
<file datatype="xml" source-language="en" target-language="cs" original="../LocalizableStrings.resx">
<body>
<trans-unit id="MSBuildServer">
<source>MSBuild server</source>
<target state="new">MSBuild server</target>
<note />
</trans-unit>
<trans-unit id="VBCSCompilerServer">
<source>VB/C# compiler server</source>
<target state="new">VB/C# compiler server</target>
<note />
</trans-unit>
<trans-unit id="RazorServer">
<source>Razor build server</source>
<target state="new">Razor build server</target>
<note />
</trans-unit>
Implement Razor server discovery by pid file. Previously, Razor server discovery for the `build-server shutdown` command was implemented by invoking MSBuild on a project file in the current directory to evaluate the path to the Razor server dll. This was problematic since it would only discover a single running Razor server instance and required that the user run the `build-server shutdown` command from a specific location. Razor's server now writes a "pid file" to a well-known location (`~/.dotnet/pids/build`) which the command can now enumerate to discover, and shutdown, the running Razor servers. This commit changes the Razor server discovery to use the pid files and removes the requirement that users need to run the command in specific directories to work. Fixes #9084.
2018-04-15 00:50:32 -07:00
<trans-unit id="ShutdownCommandFailed">
<source>The shutdown command failed: {0}</source>
<target state="new">The shutdown command failed: {0}</target>
Implement `buildserver shutdown` command. This commit implements the `buildserver shutdown` command that can be used to shutdown MSBuild, VB/C# compiler, and Razor build servers. By default, all three build servers are shut down. Options can be passed to shut down a subset of the build servers. Fixes #8185.
2018-03-27 20:26:55 -07:00
<note />
</trans-unit>
Fix Razor server shutdown on Windows. On Windows, the Razor server correctly creates the pid file with `FileAccess.Write` and `FileOptions.DeleteOnClose`. This requires a share mode of `FileShare.Write | FileShare.Delete` to open. However, the `dotnet build-server shutdown` command was opening the file with `FileShare.Read`. As a result, an `IOException` was being thrown and was not handled. This change first opens the file with the appropriate share access and also properly handles a failure to access or read the contents of the pid file. Additionally, an integration test was added to test that Razor server shutdown works as expected. Fixes #9158.
2018-04-26 17:04:37 -07:00
<trans-unit id="FailedToReadPidFile">
<source>Failed to read pid file '{0}': {1}</source>
<target state="new">Failed to read pid file '{0}': {1}</target>
<note />
</trans-unit>
Implement `buildserver shutdown` command. This commit implements the `buildserver shutdown` command that can be used to shutdown MSBuild, VB/C# compiler, and Razor build servers. By default, all three build servers are shut down. Options can be passed to shut down a subset of the build servers. Fixes #8185.
2018-03-27 20:26:55 -07:00
</body>
</file>
</xliff>
Reference in a new issue Copy permalink