Merge pull request #17850 from dotnet/master

guardrex · web-flow · commit 77c046331f3d · 2020-04-16T15:07:26.000-05:00
diff --git a/aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/BlazorSample.csproj b/aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/BlazorSample.csproj
@@ -6,10 +6,10 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="3.2.0-preview3.20168.3" />
-    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.Build" Version="3.2.0-preview3.20168.3" PrivateAssets="all" />
-    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="3.2.0-preview3.20168.3" PrivateAssets="all" />
-    <PackageReference Include="Microsoft.AspNetCore.Blazor.HttpClient" Version="3.2.0-preview3.20168.3" />
+    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="3.2.0-preview4.20210.8" />
+    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.Build" Version="3.2.0-preview4.20210.8" PrivateAssets="all" />
+    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="3.2.0-preview4.20210.8" PrivateAssets="all" />
+    <PackageReference Include="System.Net.Http.Json" Version="3.2.0-preview5.20210.3" />
   </ItemGroup>
 
 </Project>
diff --git a/aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/Pages/CallWebAPI.razor b/aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/Pages/CallWebAPI.razor
@@ -87,7 +87,7 @@ else
 
     protected override async Task OnInitializedAsync() => await GetTodoItems();
 
-    private async Task GetTodoItems() => _todoItems = await Http.GetJsonAsync<TodoItem[]>(ServiceEndpoint);
+    private async Task GetTodoItems() => _todoItems = await Http.GetFromJsonAsync<TodoItem[]>(ServiceEndpoint);
 
     private void EditItem(long id)
     {
@@ -99,15 +99,15 @@ else
     private async Task AddItem()
     {
         var addItem = new TodoItem { Name = _newItemName, IsComplete = false };
-        await Http.PostJsonAsync(ServiceEndpoint, addItem);
+        await Http.PostAsJsonAsync(ServiceEndpoint, addItem);
         _newItemName = string.Empty;
         await GetTodoItems();
         _editRowStyle = "none";
     }
 
     private async Task SaveItem()
     {
-        await Http.PutJsonAsync($"{ServiceEndpoint}/{_editItem.Id}", _editItem);
+        await Http.PutAsJsonAsync($"{ServiceEndpoint}/{_editItem.Id}", _editItem);
         await GetTodoItems();
         _editRowStyle = "none";
     }
diff --git a/aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/Program.cs b/aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/Program.cs
@@ -1,4 +1,5 @@
 ﻿using System;
+using System.Net.Http;
 using System.Collections.Generic;
 using System.Threading.Tasks;
 using System.Text;
@@ -14,7 +15,7 @@ public static async Task Main(string[] args)
             var builder = WebAssemblyHostBuilder.CreateDefault(args);
             builder.RootComponents.Add<App>("app");
 
-            builder.Services.AddBaseAddressHttpClient();
+            builder.Services.AddSingleton(new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) });
 
             await builder.Build().RunAsync();
         }
diff --git a/aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/_Imports.razor b/aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/_Imports.razor
@@ -1,4 +1,5 @@
 @using System.Net.Http
+@using System.Net.Http.Json
 @using Microsoft.AspNetCore.Components.Forms
 @using Microsoft.AspNetCore.Components.Routing
 @using Microsoft.AspNetCore.Components.Web
diff --git a/aspnetcore/blazor/debug.md b/aspnetcore/blazor/debug.md
@@ -5,7 +5,7 @@ description: Learn how to debug Blazor apps.
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 03/26/2020
+ms.date: 04/16/2020
 no-loc: [Blazor, SignalR]
 uid: blazor/debug
 ---
@@ -47,7 +47,7 @@ Debugging requires either of the following browsers:
 
 ## Enable debugging for Visual Studio and Visual Studio Code
 
-Debugging is enabled automatically for new projects that are created using the ASP.NET Core 3.2 Preview 3 or later Blazor WebAssembly project template.
+Debugging is enabled automatically for new projects that are created using the ASP.NET Core 3.2 Preview 3 or later Blazor WebAssembly project template ([current release is 3.2 Preview 4](xref:blazor/get-started)).
 
 To enable debugging for an existing Blazor WebAssembly app, update the *launchSettings.json* file in the startup project to include the following `inspectUri` property in each launch profile:
 
diff --git a/aspnetcore/blazor/get-started.md b/aspnetcore/blazor/get-started.md
@@ -5,7 +5,7 @@ description: Get started with Blazor by building a Blazor app with the tooling o
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 04/09/2020
+ms.date: 04/16/2020
 no-loc: [Blazor, SignalR]
 uid: blazor/get-started
 ---
@@ -25,6 +25,12 @@ To get started with Blazor, follow the guidance for your choice of tooling:
 
    For information on the two Blazor hosting models, *Blazor WebAssembly* and *Blazor Server*, see <xref:blazor/hosting-models>.
 
+1. Install the [Blazor WebAssembly](xref:blazor/hosting-models#blazor-webassembly) preview template by running the following command:
+
+   ```dotnetcli
+   dotnet new -i Microsoft.AspNetCore.Components.WebAssembly.Templates::3.2.0-preview4.20210.8
+   ```
+
 1. Create a new project.
 
 1. Select **Blazor App**. Select **Next**.
@@ -42,11 +48,11 @@ To get started with Blazor, follow the guidance for your choice of tooling:
 1. Optionally install the [Blazor WebAssembly](xref:blazor/hosting-models#blazor-webassembly) preview template by running the following command:
 
    ```dotnetcli
-   dotnet new -i Microsoft.AspNetCore.Components.WebAssembly.Templates::3.2.0-preview3.20168.3
+   dotnet new -i Microsoft.AspNetCore.Components.WebAssembly.Templates::3.2.0-preview4.20210.8
    ```
 
    > [!NOTE]
-   > The [.NET Core SDK version 3.1.201 or later](https://dotnet.microsoft.com/download/dotnet-core/3.1) is **required** to use the 3.2 Preview 3 Blazor WebAssembly template. Confirm the installed .NET Core SDK version by running `dotnet --version` in a command shell.
+   > The [.NET Core SDK version 3.1.201 or later](https://dotnet.microsoft.com/download/dotnet-core/3.1) is **required** to use the 3.2 Preview 4 Blazor WebAssembly template. Confirm the installed .NET Core SDK version by running `dotnet --version` in a command shell.
 
 1. Install [Visual Studio Code](https://code.visualstudio.com/).
 
@@ -105,11 +111,11 @@ If a prompt appears to trust the development certificate, trust the certificate
 1. Optionally install the [Blazor WebAssembly](xref:blazor/hosting-models#blazor-webassembly) preview template by running the following command:
 
    ```dotnetcli
-   dotnet new -i Microsoft.AspNetCore.Components.WebAssembly.Templates::3.2.0-preview3.20168.3
+   dotnet new -i Microsoft.AspNetCore.Components.WebAssembly.Templates::3.2.0-preview4.20210.8
    ```
 
    > [!NOTE]
-   > The [.NET Core SDK version 3.1.201 or later](https://dotnet.microsoft.com/download/dotnet-core/3.1) is **required** to use the 3.2 Preview 3 Blazor WebAssembly template. Confirm the installed .NET Core SDK version by running `dotnet --version` in a command shell.
+   > The [.NET Core SDK version 3.1.201 or later](https://dotnet.microsoft.com/download/dotnet-core/3.1) is **required** to use the 3.2 Preview 4 Blazor WebAssembly template. Confirm the installed .NET Core SDK version by running `dotnet --version` in a command shell.
 
 1. For a Blazor Server experience, execute the following commands in a command shell:
 
diff --git a/aspnetcore/blazor/hosting-model-configuration.md b/aspnetcore/blazor/hosting-model-configuration.md
@@ -5,7 +5,7 @@ description: Learn about Blazor hosting model configuration, including how to in
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 04/07/2020
+ms.date: 04/16/2020
 no-loc: [Blazor, SignalR]
 uid: blazor/hosting-model-configuration
 ---
@@ -62,7 +62,7 @@ Obtain the app's environment in a component by injecting `IWebAssemblyHostEnviro
 
 ### Configuration
 
-As of the ASP.NET Core 3.2 Preview 3 release, Blazor WebAssembly supports configuration from:
+As of the ASP.NET Core 3.2 Preview 3 release ([current release is 3.2 Preview 4](xref:blazor/get-started)), Blazor WebAssembly supports configuration from:
 
 * *wwwroot/appsettings.json*
 * *wwwroot/appsettings.{ENVIRONMENT}.json*
diff --git a/aspnetcore/client-side/bundling-and-minification.md b/aspnetcore/client-side/bundling-and-minification.md
@@ -4,7 +4,7 @@ author: scottaddie
 description: Learn how to optimize static resources in an ASP.NET Core web application by applying bundling and minification techniques.
 ms.author: scaddie
 ms.custom: mvc
-ms.date: 06/17/2019
+ms.date: 04/15/2020
 uid: client-side/bundling-and-minification
 ---
 # Bundle and minify static assets in ASP.NET Core
@@ -57,7 +57,7 @@ Browsers are fairly verbose with regard to HTTP request headers. The total bytes
 
 ## Choose a bundling and minification strategy
 
-The MVC and Razor Pages project templates provide an out-of-the-box solution for bundling and minification consisting of a JSON configuration file. Third-party tools, such as the [Grunt](xref:client-side/using-grunt) task runner, accomplish the same tasks with a bit more complexity. A third-party tool is a great fit when your development workflow requires processing beyond bundling and minification&mdash;such as linting and image optimization. By using design-time bundling and minification, the minified files are created prior to the app's deployment. Bundling and minifying before deployment provides the advantage of reduced server load. However, it's important to recognize that design-time bundling and minification increases build complexity and only works with static files.
+The MVC and Razor Pages project templates provide a solution for bundling and minification consisting of a JSON configuration file. Third-party tools, such as the [Grunt](xref:client-side/using-grunt) task runner, accomplish the same tasks with a bit more complexity. A third-party tool is a great fit when your development workflow requires processing beyond bundling and minification&mdash;such as linting and image optimization. By using design-time bundling and minification, the minified files are created prior to the app's deployment. Bundling and minifying before deployment provides the advantage of reduced server load. However, it's important to recognize that design-time bundling and minification increases build complexity and only works with static files.
 
 ## Configure bundling and minification
 
@@ -90,109 +90,6 @@ Configuration options include:
 * `sourceMap`: Flag indicating whether to generate a source map for the bundled file. **optional**, *default - false*
 * `sourceMapRootPath`: The root path for storing the generated source map file.
 
-## Build-time execution of bundling and minification
-
-The [BuildBundlerMinifier](https://www.nuget.org/packages/BuildBundlerMinifier/) NuGet package enables the execution of bundling and minification at build time. The package injects [MSBuild Targets](/visualstudio/msbuild/msbuild-targets) which run at build and clean time. The *bundleconfig.json* file is analyzed by the build process to produce the output files based on the defined configuration.
-
-> [!NOTE]
-> BuildBundlerMinifier belongs to a community-driven project on GitHub for which Microsoft provides no support. Issues should be filed [here](https://github.com/madskristensen/BundlerMinifier/issues).
-
-# [Visual Studio](#tab/visual-studio)
-
-Add the *BuildBundlerMinifier* package to your project.
-
-Build the project. The following appears in the Output window:
-
-```console
-1>------ Build started: Project: BuildBundlerMinifierApp, Configuration: Debug Any CPU ------
-1>
-1>Bundler: Begin processing bundleconfig.json
-1>  Minified wwwroot/css/site.min.css
-1>  Minified wwwroot/js/site.min.js
-1>Bundler: Done processing bundleconfig.json
-1>BuildBundlerMinifierApp -> C:\BuildBundlerMinifierApp\bin\Debug\netcoreapp2.0\BuildBundlerMinifierApp.dll
-========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
-```
-
-Clean the project. The following appears in the Output window:
-
-```console
-1>------ Clean started: Project: BuildBundlerMinifierApp, Configuration: Debug Any CPU ------
-1>
-1>Bundler: Cleaning output from bundleconfig.json
-1>Bundler: Done cleaning output file from bundleconfig.json
-========== Clean: 1 succeeded, 0 failed, 0 skipped ==========
-```
-
-# [.NET Core CLI](#tab/netcore-cli)
-
-Add the *BuildBundlerMinifier* package to your project:
-
-```dotnetcli
-dotnet add package BuildBundlerMinifier
-```
-
-If using ASP.NET Core 1.x, restore the newly added package:
-
-```dotnetcli
-dotnet restore
-```
-
-Build the project:
-
-```dotnetcli
-dotnet build
-```
-
-The following appears:
-
-```console
-Microsoft (R) Build Engine version 15.4.8.50001 for .NET Core
-Copyright (C) Microsoft Corporation. All rights reserved.
-
-
-    Bundler: Begin processing bundleconfig.json
-    Bundler: Done processing bundleconfig.json
-    BuildBundlerMinifierApp -> C:\BuildBundlerMinifierApp\bin\Debug\netcoreapp2.0\BuildBundlerMinifierApp.dll
-```
-
-Clean the project:
-
-```dotnetcli
-dotnet clean
-```
-
-The following output appears:
-
-```console
-Microsoft (R) Build Engine version 15.4.8.50001 for .NET Core
-Copyright (C) Microsoft Corporation. All rights reserved.
-
-
-  Bundler: Cleaning output from bundleconfig.json
-  Bundler: Done cleaning output file from bundleconfig.json
-```
-
----
-
-## Ad hoc execution of bundling and minification
-
-It's possible to run the bundling and minification tasks on an ad hoc basis, without building the project. Add the [BundlerMinifier.Core](https://www.nuget.org/packages/BundlerMinifier.Core/) NuGet package to your project:
-
-[!code-xml[](../client-side/bundling-and-minification/samples/BuildBundlerMinifierApp/BuildBundlerMinifierApp.csproj?range=10)]
-
-> [!NOTE]
-> BundlerMinifier.Core belongs to a community-driven project on GitHub for which Microsoft provides no support. Issues should be filed [here](https://github.com/madskristensen/BundlerMinifier/issues).
-
-This package extends the .NET Core CLI to include the *dotnet-bundle* tool. The following command can be executed in the Package Manager Console (PMC) window or in a command shell:
-
-```dotnetcli
-dotnet bundle
-```
-
-> [!IMPORTANT]
-> NuGet Package Manager adds dependencies to the *.csproj file as `<PackageReference />` nodes. The `dotnet bundle` command is registered with the .NET Core CLI only when a `<DotNetCliToolReference />` node is used. Modify the *.csproj file accordingly.
-
 ## Add files to workflow
 
 Consider an example in which an additional *custom.css* file is added resembling the following:
@@ -252,32 +149,7 @@ The following `environment` tag renders the bundled and minified CSS files when
 
 There are cases in which an app's bundling and minification workflow requires additional processing. Examples include image optimization, cache busting, and CDN asset processing. To satisfy these requirements, you can convert the bundling and minification workflow to use Gulp.
 
-### Use the Bundler & Minifier extension
-
-The Visual Studio [Bundler & Minifier](https://marketplace.visualstudio.com/items?itemName=MadsKristensen.BundlerMinifier) extension handles the conversion to Gulp.
-
-> [!NOTE]
-> The Bundler & Minifier extension belongs to a community-driven project on GitHub for which Microsoft provides no support. Issues should be filed [here](https://github.com/madskristensen/BundlerMinifier/issues).
-
-Right-click the *bundleconfig.json* file in Solution Explorer and select **Bundler & Minifier** > **Convert To Gulp...**:
-
-![Convert To Gulp context menu item](../client-side/bundling-and-minification/_static/convert-to-gulp.png)
-
-The *gulpfile.js* and *package.json* files are added to the project. The supporting [npm](https://www.npmjs.com/) packages listed in the *package.json* file's `devDependencies` section are installed.
-
-Run the following command in the PMC window to install the Gulp CLI as a global dependency:
-
-```console
-npm i -g gulp-cli
-```
-
-The *gulpfile.js* file reads the *bundleconfig.json* file for the inputs, outputs, and settings.
-
-[!code-javascript[](../client-side/bundling-and-minification/samples/BuildBundlerMinifierApp/gulpfile.js?range=1-12&highlight=10)]
-
-### Convert manually
-
-If Visual Studio and/or the Bundler & Minifier extension aren't available, convert manually.
+### Manually convert the bundling and minification workflow to use Gulp
 
 Add a *package.json* file, with the following `devDependencies`, to the project root:
 
diff --git a/aspnetcore/fundamentals/host/generic-host.md b/aspnetcore/fundamentals/host/generic-host.md
@@ -12,7 +12,7 @@ uid: fundamentals/host/generic-host
 
 ::: moniker range=">= aspnetcore-3.0 <= aspnetcore-3.1"
 
-The ASP.NET Core templates create a .NET Core Generic Host (<xref:Microsoft.Extensions.Hosting.HostBuilder>).
+The ASP.NET Core templates create a .NET Core Generic Host, <xref:Microsoft.Extensions.Hosting.HostBuilder>.
 
 ## Host definition
 
@@ -34,7 +34,7 @@ The host is typically configured, built, and run by code in the `Program` class.
 * Calls a `CreateHostBuilder` method to create and configure a builder object.
 * Calls `Build` and `Run` methods on the builder object.
 
-The ASP.NET Core web templates generate the following code to create a host:
+The ASP.NET Core web templates generate the following code to create a Generic Host:
 
 ```csharp
 public class Program
@@ -53,7 +53,7 @@ public class Program
 }
 ```
 
-The following code creates a non-HTTP workload with a `IHostedService` implementation added to the DI container.
+The following code creates a Generic Host using non-HTTP workload. The `IHostedService` implementation is added to the DI container:
 
 ```csharp
 public class Program
@@ -83,6 +83,8 @@ public static IHostBuilder CreateHostBuilder(string[] args) =>
         });
 ```
 
+The preceding code is generated by the ASP.NET Core templates.
+
 If the app uses Entity Framework Core, don't change the name or signature of the `CreateHostBuilder` method. The [Entity Framework Core tools](/ef/core/miscellaneous/cli/) expect to find a `CreateHostBuilder` method that configures the host without running the app. For more information, see [Design-time DbContext Creation](/ef/core/miscellaneous/cli/dbcontext-creation).
 
 ## Default builder settings
diff --git a/aspnetcore/grpc/browser/sample/CORS_Startup.cs b/aspnetcore/grpc/browser/sample/CORS_Startup.cs
@@ -8,7 +8,7 @@ public void ConfigureServices(IServiceCollection services)
         builder.AllowAnyOrigin()
                .AllowAnyMethod()
                .AllowAnyHeader()
-               .WithExposedHeaders("Grpc-Status", "Grpc-Message");
+               .WithExposedHeaders("Grpc-Status", "Grpc-Message", "Grpc-Encoding", "Grpc-Accept-Encoding");
     }));
 }
 
diff --git a/aspnetcore/host-and-deploy/blazor/webassembly.md b/aspnetcore/host-and-deploy/blazor/webassembly.md
@@ -5,7 +5,7 @@ description: Learn how to host and deploy a Blazor app using ASP.NET Core, Conte
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 04/06/2020
+ms.date: 04/16/2020
 no-loc: [Blazor, SignalR]
 uid: host-and-deploy/blazor/webassembly
 ---
@@ -17,14 +17,18 @@ By [Luke Latham](https://github.com/guardrex), [Rainer Stropek](https://www.time
 
 With the [Blazor WebAssembly hosting model](xref:blazor/hosting-models#blazor-webassembly):
 
-* The Blazor app, its dependencies, and the .NET runtime are downloaded to the browser.
+* The Blazor app, its dependencies, and the .NET runtime are downloaded to the browser in parallel.
 * The app is executed directly on the browser UI thread.
 
 The following deployment strategies are supported:
 
 * The Blazor app is served by an ASP.NET Core app. This strategy is covered in the [Hosted deployment with ASP.NET Core](#hosted-deployment-with-aspnet-core) section.
 * The Blazor app is placed on a static hosting web server or service, where .NET isn't used to serve the Blazor app. This strategy is covered in the [Standalone deployment](#standalone-deployment) section, which includes information on hosting a Blazor WebAssembly app as an IIS sub-app.
 
+## Brotli precompression
+
+When a Blazor WebAssembly app is published, the output is precompressed using the [Brotli compression algorithm](https://tools.ietf.org/html/rfc7932) at the highest level to reduce the app size and remove the need for runtime compression.
+
 ## Rewrite URLs for correct routing
 
 Routing requests for page components in a Blazor WebAssembly app isn't as straightforward as routing requests in a Blazor Server, hosted app. Consider a Blazor WebAssembly app with two components:
diff --git a/aspnetcore/includes/blazorwasm-3.2-template-article-notice.md b/aspnetcore/includes/blazorwasm-3.2-template-article-notice.md
@@ -1,2 +1,2 @@
 > [!NOTE]
-> The guidance in this article applies to the ASP.NET Core Blazor WebAssembly template version 3.2 or later. To obtain the latest Blazor WebAssembly template (version `3.2.0-preview3.20168.3`) when not using Visual Studio version 16.6 Preview 2 or later, see <xref:blazor/get-started>.
+> The guidance in this article applies to the ASP.NET Core Blazor WebAssembly template version 3.2 or later. To obtain the latest Blazor WebAssembly template (version `3.2.0-preview4.20210.8`) when not using Visual Studio version 16.6 Preview 2 or later, see <xref:blazor/get-started>.
diff --git a/aspnetcore/includes/blazorwasm-3.2-template-section-notice.md b/aspnetcore/includes/blazorwasm-3.2-template-section-notice.md
diff --git a/aspnetcore/index.yml b/aspnetcore/index.yml
diff --git a/aspnetcore/migration/22-to-30.md b/aspnetcore/migration/22-to-30.md
diff --git a/aspnetcore/security/authorization/policies.md b/aspnetcore/security/authorization/policies.md
diff --git a/aspnetcore/tutorials/razor-pages/model.md b/aspnetcore/tutorials/razor-pages/model.md
diff --git a/aspnetcore/tutorials/signalr-blazor-webassembly.md b/aspnetcore/tutorials/signalr-blazor-webassembly.md

Original file line number	Diff line number	Diff line change
`@@ -87,7 +87,7 @@ else`
`87`	`87`
`88`	`88`	`protected override async Task OnInitializedAsync() => await GetTodoItems();`
`89`	`89`
`90`		`- private async Task GetTodoItems() => _todoItems = await Http.GetJsonAsync<TodoItem[]>(ServiceEndpoint);`
	`90`	`+ private async Task GetTodoItems() => _todoItems = await Http.GetFromJsonAsync<TodoItem[]>(ServiceEndpoint);`
`91`	`91`
`92`	`92`	`private void EditItem(long id)`
`93`	`93`	`{`
`@@ -99,15 +99,15 @@ else`
`99`	`99`	`private async Task AddItem()`
`100`	`100`	`{`
`101`	`101`	`var addItem = new TodoItem { Name = _newItemName, IsComplete = false };`
`102`		`- await Http.PostJsonAsync(ServiceEndpoint, addItem);`
	`102`	`+ await Http.PostAsJsonAsync(ServiceEndpoint, addItem);`
`103`	`103`	`_newItemName = string.Empty;`
`104`	`104`	`await GetTodoItems();`
`105`	`105`	`_editRowStyle = "none";`
`106`	`106`	`}`
`107`	`107`
`108`	`108`	`private async Task SaveItem()`
`109`	`109`	`{`
`110`		`- await Http.PutJsonAsync($"{ServiceEndpoint}/{_editItem.Id}", _editItem);`
	`110`	`+ await Http.PutAsJsonAsync($"{ServiceEndpoint}/{_editItem.Id}", _editItem);`
`111`	`111`	`await GetTodoItems();`
`112`	`112`	`_editRowStyle = "none";`
`113`	`113`	`}`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`@using System.Net.Http`
	`2`	`+@using System.Net.Http.Json`
`2`	`3`	`@using Microsoft.AspNetCore.Components.Forms`
`3`	`4`	`@using Microsoft.AspNetCore.Components.Routing`
`4`	`5`	`@using Microsoft.AspNetCore.Components.Web`
Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,7 @@ public void ConfigureServices(IServiceCollection services)`
`8`	`8`	`builder.AllowAnyOrigin()`
`9`	`9`	`.AllowAnyMethod()`
`10`	`10`	`.AllowAnyHeader()`
`11`		`- .WithExposedHeaders("Grpc-Status", "Grpc-Message");`
	`11`	`+ .WithExposedHeaders("Grpc-Status", "Grpc-Message", "Grpc-Encoding", "Grpc-Accept-Encoding");`
`12`	`12`	`}));`
`13`	`13`	`}`
`14`	`14`