dotnet-installer/TestAssets/TestProjects/TestRazorApp/TestRazorApp.csproj

<Project Sdk="Microsoft.NET.Sdk.Razor">
  <PropertyGroup>
    <TargetFramework>netcoreapp3.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
  </ItemGroup>
</Project>
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			`<Project Sdk="Microsoft.NET.Sdk.Razor">`
			`<PropertyGroup>`
Update ASP.NET Core to 3.0.0-alpha1-10772 2018-11-20 17:15:37 -08:00			`<TargetFramework>netcoreapp3.0</TargetFramework>`
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			`</PropertyGroup>`

			`<ItemGroup>`
Update ASP.NET Core to 3.0.0-alpha1-10772 2018-11-20 17:15:37 -08:00			`<FrameworkReference Include="Microsoft.AspNetCore.App" />`
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			`</ItemGroup>`
			`</Project>`