dotnet · guardrex · May 5, 2025 · Apr 29, 2025 · Apr 29, 2025 · Apr 29, 2025
diff --git a/aspnetcore/blazor/call-web-api.md b/aspnetcore/blazor/call-web-api.md
@@ -22,14 +22,25 @@ The [`System.Net.Http.Json`](https://www.nuget.org/packages/System.Net.Http.Json
 
 ## Use a token handler for web API calls
 
-Blazor Web Apps with OIDC authentication can use a token handler approach to make outgoing requests to secure external web API calls. This approach is used by the `BlazorWebAppOidc` and `BlazorWebAppOidcServer` sample apps described in the next section.
+Blazor Web Apps with OIDC authentication can use a token handler approach to make outgoing requests to secure external web API calls. This approach is used by the `BlazorWebAppOidc` and `BlazorWebAppOidcServer` sample apps described in the *Sample apps* section of this article.
 
 For more information, see the following resources:
 
 * <xref:blazor/security/additional-scenarios#use-a-token-handler-for-web-api-calls>
 * *Secure an ASP.NET Core Blazor Web App with OpenID Connect (OIDC)*
-  * [Non-BFF pattern (Interactive Auto)](xref:blazor/security/blazor-web-app-oidc?view=aspnetcore-9.0&pivots=non-bff-pattern)
-  * [Non-BFF pattern (Interactive Server)](xref:blazor/security/blazor-web-app-oidc?view=aspnetcore-9.0&pivots=non-bff-pattern-server)
+  * [Non-BFF pattern (Interactive Auto)](xref:blazor/security/blazor-web-app-oidc?pivots=non-bff-pattern)
+  * [Non-BFF pattern (Interactive Server)](xref:blazor/security/blazor-web-app-oidc?pivots=non-bff-pattern-server)
+
+## Microsoft identity platform for web API calls
+
+Blazor Web Apps that use use [Microsoft identity platform](/entra/identity-platform/)/[Microsoft Identity Web packages](/entra/msal/dotnet/microsoft-identity-web/) for [Microsoft Entra ID](https://www.microsoft.com/security/business/microsoft-entra) can make streamlined calls using Entra-specific API. This approach is used by the `BlazorWebAppEntra` and `BlazorWebAppEntraBff` sample apps described in the *Sample apps* section of this article.
+
+For more information, see the following resources:
+
+* <xref:blazor/security/additional-scenarios#use-a-token-handler-for-web-api-calls>
+* *Secure an ASP.NET Core Blazor Web App with Microsoft Entra ID*
+  * [Non-BFF pattern (Interactive Auto)](xref:blazor/security/blazor-web-app-entra?pivots=non-bff-pattern)
+  * [BFF pattern (Interactive Auto)](xref:blazor/security/blazor-web-app-entra?pivots=non-bff-pattern-server)
 
 ## Sample apps
 

diff --git a/aspnetcore/blazor/components/built-in-components.md b/aspnetcore/blazor/components/built-in-components.md
@@ -37,7 +37,7 @@ The following built-in Razor components are provided by the Blazor framework. Fo
 * [`InputSelect`](xref:blazor/forms/input-components)
 * [`InputText`](xref:blazor/forms/input-components)
 * [`InputTextArea`](xref:blazor/forms/input-components)
-* [`LayoutComponentBase`](xref:blazor/components/layouts#layout-components)
+* [`LayoutComponentBase`](xref:blazor/components/layouts#create-a-layout-component)
 * [`LayoutView`](xref:blazor/components/layouts#apply-a-layout-to-arbitrary-content-layoutview-component)
 * [`NavigationLock`](xref:blazor/fundamentals/routing#handleprevent-location-changes)
 * [`NavLink`](xref:blazor/fundamentals/routing#navlink-component)
@@ -77,7 +77,7 @@ The following built-in Razor components are provided by the Blazor framework. Fo
 * [`InputSelect`](xref:blazor/forms/input-components)
 * [`InputText`](xref:blazor/forms/input-components)
 * [`InputTextArea`](xref:blazor/forms/input-components)
-* [`LayoutComponentBase`](xref:blazor/components/layouts#layout-components)
+* [`LayoutComponentBase`](xref:blazor/components/layouts#create-a-layout-component)
 * [`LayoutView`](xref:blazor/components/layouts#apply-a-layout-to-arbitrary-content-layoutview-component)
 * [`NavigationLock`](xref:blazor/fundamentals/routing#handleprevent-location-changes)
 * [`NavLink`](xref:blazor/fundamentals/routing#navlink-component)
@@ -115,7 +115,7 @@ The following built-in Razor components are provided by the Blazor framework. Fo
 * [`InputSelect`](xref:blazor/forms/input-components)
 * [`InputText`](xref:blazor/forms/input-components)
 * [`InputTextArea`](xref:blazor/forms/input-components)
-* [`LayoutComponentBase`](xref:blazor/components/layouts#layout-components)
+* [`LayoutComponentBase`](xref:blazor/components/layouts#create-a-layout-component)
 * [`LayoutView`](xref:blazor/components/layouts#apply-a-layout-to-arbitrary-content-layoutview-component)
 * [`NavigationLock`](xref:blazor/fundamentals/routing#handleprevent-location-changes)
 * [`NavLink`](xref:blazor/fundamentals/routing#navlink-component)
@@ -149,7 +149,7 @@ The following built-in Razor components are provided by the Blazor framework. Fo
 * [`InputSelect`](xref:blazor/forms/input-components)
 * [`InputText`](xref:blazor/forms/input-components)
 * [`InputTextArea`](xref:blazor/forms/input-components)
-* [`LayoutComponentBase`](xref:blazor/components/layouts#layout-components)
+* [`LayoutComponentBase`](xref:blazor/components/layouts#create-a-layout-component)
 * [`LayoutView`](xref:blazor/components/layouts#apply-a-layout-to-arbitrary-content-layoutview-component)
 * [`NavLink`](xref:blazor/fundamentals/routing#navlink-component)
 * [`OwningComponentBase`](xref:fundamentals/dependency-injection#utility-base-component-classes-to-manage-a-di-scope)
@@ -177,7 +177,7 @@ The following built-in Razor components are provided by the Blazor framework. Fo
 * [`InputSelect`](xref:blazor/forms/input-components)
 * [`InputText`](xref:blazor/forms/input-components)
 * [`InputTextArea`](xref:blazor/forms/input-components)
-* [`LayoutComponentBase`](xref:blazor/components/layouts#layout-components)
+* [`LayoutComponentBase`](xref:blazor/components/layouts#create-a-layout-component)
 * [`LayoutView`](xref:blazor/components/layouts#apply-a-layout-to-arbitrary-content-layoutview-component)
 * [`NavLink`](xref:blazor/fundamentals/routing#navlink-component)
 * [`OwningComponentBase`](xref:fundamentals/dependency-injection#utility-base-component-classes-to-manage-a-di-scope)
@@ -203,7 +203,7 @@ The following built-in Razor components are provided by the Blazor framework. Fo
 * [`InputSelect`](xref:blazor/forms/input-components)
 * [`InputText`](xref:blazor/forms/input-components)
 * [`InputTextArea`](xref:blazor/forms/input-components)
-* [`LayoutComponentBase`](xref:blazor/components/layouts#layout-components)
+* [`LayoutComponentBase`](xref:blazor/components/layouts#create-a-layout-component)
 * [`LayoutView`](xref:blazor/components/layouts#apply-a-layout-to-arbitrary-content-layoutview-component)
 * [`NavLink`](xref:blazor/fundamentals/routing#navlink-component)
 * [`OwningComponentBase`](xref:fundamentals/dependency-injection#utility-base-component-classes-to-manage-a-di-scope)

diff --git a/aspnetcore/blazor/components/event-handling.md b/aspnetcore/blazor/components/event-handling.md
@@ -40,6 +40,9 @@ For event handling:
 
 :::moniker-end
 
+> [!IMPORTANT]
+> The Blazor framework doesn't track `void`-returning asynchronous methods (`async`). As a result, the entire process fails when an exception isn't caught if `void` is returned. Always return a <xref:System.Threading.Tasks.Task>/<xref:System.Threading.Tasks.ValueTask> from asynchronous methods.
+
 The following code:
 
 * Calls the `UpdateHeading` method when the button is selected in the UI.

diff --git a/aspnetcore/blazor/components/index.md b/aspnetcore/blazor/components/index.md
@@ -638,7 +638,7 @@ Razor syntax for C# control structures, directives, and directive attributes are
 
 ### Asynchronous methods (`async`) don't support returning `void`
 
-The Blazor framework doesn't track `void`-returning asynchronous methods (`async`). As a result, exceptions aren't caught if `void` is returned. Always return a <xref:System.Threading.Tasks.Task> from asynchronous methods.
+The Blazor framework doesn't track `void`-returning asynchronous methods (`async`). As a result, the entire process fails when an exception isn't caught if `void` is returned. Always return a <xref:System.Threading.Tasks.Task>/<xref:System.Threading.Tasks.ValueTask> from asynchronous methods.
 
 ### Nested components
 

diff --git a/aspnetcore/blazor/components/layouts.md b/aspnetcore/blazor/components/layouts.md
@@ -20,9 +20,7 @@ Some app elements, such as menus, copyright messages, and company logos, are usu
 
 A Blazor layout is a Razor component that shares markup with components that reference it. Layouts can use [data binding](xref:blazor/components/data-binding), [dependency injection](xref:blazor/fundamentals/dependency-injection), and other features of components.
 
-## Layout components
-
-### Create a layout component
+## Create a layout component
 
 To create a layout component:
 
@@ -73,7 +71,7 @@ The following `DoctorWhoLayout` component shows the Razor template of a layout c
 
 :::moniker-end
 
-### `MainLayout` component
+## `MainLayout` component
 
 In an app created from a [Blazor project template](xref:blazor/project-structure), the `MainLayout` component is the app's [default layout](#apply-a-default-layout-to-an-app). Blazor's layout adopts the [:::no-loc text="Flexbox"::: layout model](https://developer.mozilla.org/docs/Glossary/Flexbox) ([W3C specification](https://www.w3.org/TR/css-flexbox-1/)).
 
@@ -94,6 +92,86 @@ In an app created from a [Blazor project template](xref:blazor/project-structure
 
 :::moniker-end
 
+:::moniker range=">= aspnetcore-8.0"
+
+<!-- UPDATE 11.0 Is https://github.com/dotnet/aspnetcore/issues/52768 addressed
+                 to resolve the following limitation? -->
+
+## Statically-rendered layout components
+
+When a Blazor Web App adopts per-page/component rendering (the `Routes` component doesn't specify an interactive render mode), layout components are rendered statically on the server. Applying an interactive render mode directly to a layout isn't supported because Blazor doesn't support serializing a <xref:Microsoft.AspNetCore.Components.RenderFragment> (`@Body` in this case) as a root component parameter. For example, placing `@rendermode InteractiveServer` at the top of the `MainLayout` component results in the following runtime exception:
+
+> :::no-loc text="System.InvalidOperationException: Cannot pass the parameter 'Body' to component 'MainLayout' with rendermode 'InteractiveServerRenderMode'. This is because the parameter is of the delegate type 'Microsoft.AspNetCore.Components.RenderFragment', which is arbitrary code and cannot be serialized.":::
+
+This applies to any layout component that inherits from <xref:Microsoft.AspNetCore.Components.LayoutComponentBase> in an app that adopts per-page/component rendering.
+
+This scenario might be addressed in a future release of Blazor. For more information, see [[Blazor] Support serializing render fragments from SSR (`dotnet/aspnetcore` #52768)](https://github.com/dotnet/aspnetcore/issues/52768). In the meantime, you can adopt the following approach in a Blazor Web App that adopts per-page/component rendering.
+
+Create a wrapper component that's capable of interactivity. In the following example, a wrapper component contains a [Blazor section](xref:blazor/components/sections) that can receive content from a child component.
+
+In the `_Imports.razor` file, add an [`@using`](xref:mvc/views/razor#using) directive for sections (<xref:Microsoft.AspNetCore.Components.Sections?displayProperty=fullName>):
+
+```razor
+@using Microsoft.AspNetCore.Components.Sections
+```
+
+Create the following interactive wrapper component in the `Pages` folder.
+
+`Pages/InteractiveWrapper.razor`:
+
+```razor
+@rendermode InteractiveServer
+
+<div>
+    <SectionOutlet SectionName="top-bar" />
+</div>
+
+@ChildContent
+
+@code {
+    [Parameter]
+    public RenderFragment? ChildContent { get; set; }
+}
+```
+
+The `Counter` component can use the wrapper component and set interactive section content. In the following example, a counter button is placed in the section.
+
+`Pages/Counter.razor`:
+
+```razor
+@page "/counter"
+@rendermode InteractiveServer
+
+<InteractiveWrapper>
+
+    <SectionContent SectionName="top-bar">
+        <button class="btn btn-primary" @onclick="IncrementCount">Click me</button>
+    </SectionContent>
+
+    <PageTitle>Counter</PageTitle>
+
+    <h1>Counter</h1>
+
+    <p role="status">Current count: @currentCount</p>
+
+    <button class="btn btn-primary" @onclick="IncrementCount">Click me</button>
+
+</InteractiveWrapper>
+
+@code {
+    private int currentCount = 0;
+
+    private void IncrementCount()
+    {
+        currentCount++;
+    }
+}
+```
+
+Other components around the app can also wrap content in the `InteractiveWrapper` component and set interactive section content.
+
+:::moniker-end
+
 ## Apply a layout
 
 ### Make the layout namespace available
@@ -220,7 +298,7 @@ Specify the default app layout in the <xref:Microsoft.AspNetCore.Components.Rout
 <RouteView RouteData="routeData" DefaultLayout="typeof({LAYOUT})" />
 ```
 
-In the preceding example, the `{LAYOUT}` placeholder is the layout (for example, `DoctorWhoLayout` if the layout file name is `DoctorWhoLayout.razor`). You may need to idenfity the layout's namespace depending on the .NET version and type of Blazor app. For more information, see the [Make the layout namespace available](#make-the-layout-namespace-available) section.
+In the preceding example, the `{LAYOUT}` placeholder is the layout (for example, `DoctorWhoLayout` if the layout file name is `DoctorWhoLayout.razor`). You may need to identify the layout's namespace depending on the .NET version and type of Blazor app. For more information, see the [Make the layout namespace available](#make-the-layout-namespace-available) section.
 
 Specifying the layout as a default layout in the <xref:Microsoft.AspNetCore.Components.Routing.Router> component's <xref:Microsoft.AspNetCore.Components.RouteView> is a useful practice because you can override the layout on a per-component or per-folder basis, as described in the preceding sections of this article. We recommend using the <xref:Microsoft.AspNetCore.Components.Routing.Router> component to set the app's default layout because it's the most general and flexible approach for using layouts.
 

diff --git a/aspnetcore/blazor/components/render-modes.md b/aspnetcore/blazor/components/render-modes.md
@@ -576,6 +576,11 @@ Non-serializable component parameters, such as child content or a render fragmen
 
 > :::no-loc text="System.InvalidOperationException: Cannot pass the parameter 'ChildContent' to component 'SharedMessage' with rendermode 'InteractiveServerRenderMode'. This is because the parameter is of the delegate type 'Microsoft.AspNetCore.Components.RenderFragment', which is arbitrary code and cannot be serialized.":::
 
+<!-- UPDATE 11.0 Is https://github.com/dotnet/aspnetcore/issues/52768 addressed
+                 to resolve the following limitation? -->
+
+The same thing happens if you attempt to adopt interactive rendering in a layout that inherits from <xref:Microsoft.AspNetCore.Components.LayoutComponentBase>, such as the app's `MainLayout` component, in an app that adopts per-page/component rendering. For more information, see <xref:blazor/components/layouts#statically-rendered-layout-components>.
+
 To circumvent the preceding limitation, wrap the child component in another component that doesn't have the parameter. This is the approach taken in the Blazor Web App project template with the `Routes` component (`Components/Routes.razor`) to wrap the <xref:Microsoft.AspNetCore.Components.Routing.Router> component.
 
 `WrapperComponent.razor`:

diff --git a/aspnetcore/blazor/components/sections.md b/aspnetcore/blazor/components/sections.md
@@ -92,3 +92,4 @@ A section interacts with other Blazor features in the following ways:
 * [Cascading values](xref:blazor/components/cascading-values-and-parameters) flow into section content from where the content is defined by the <xref:Microsoft.AspNetCore.Components.Sections.SectionContent> component.
 * Unhandled exceptions are handled by [error boundaries](xref:blazor/fundamentals/handle-errors#error-boundaries) defined around a <xref:Microsoft.AspNetCore.Components.Sections.SectionContent> component.
 * A Razor component configured for [streaming rendering](xref:blazor/components/rendering#streaming-rendering) also configures section content provided by a <xref:Microsoft.AspNetCore.Components.Sections.SectionContent> component to use streaming rendering.
+* A section that contains interactive components is statically rendered (non-functional) in a layout component in a Blazor Web App that adopts per-page/component rendering. For more information, see <xref:blazor/components/layouts#statically-rendered-layout-components>.
diff --git a/aspnetcore/blazor/host-and-deploy/index.md b/aspnetcore/blazor/host-and-deploy/index.md
@@ -68,8 +68,8 @@ To host a Blazor app in IIS, see the following resources:
 * IIS hosting
   * <xref:tutorials/publish-to-iis>
   * <xref:host-and-deploy/iis/index>
-* <xref:blazor/host-and-deploy/server/index>: Server apps running on IIS, including IIS with Azure Virtual Machines (VMs) running Windows OS and Azure App Service.
-* <xref:blazor/host-and-deploy/webassembly/index>: Includes additional guidance for Blazor WebAssembly apps hosted on IIS, including static site hosting, custom `web.config` files, URL rewriting, sub-apps, compression, and Azure Storage static file hosting.
+* <xref:blazor/host-and-deploy/server/index>: Blazor Web Apps (.NET 8 or later) and Blazor Server apps (.NET 7 or earlier) running on IIS, including IIS with Azure Virtual Machines (VMs) running Windows OS and Azure App Service.
+* <xref:blazor/host-and-deploy/webassembly/iis>: Standalone Blazor WebAssembly apps (all .NET releases) and hosted Blazor WebAssembly apps (.NET 7 or earlier).
 * IIS sub-application hosting
   * Follow the [app base path guidance](xref:blazor/host-and-deploy/app-base-path) prior to publishing the app. The examples use an app base path of `/CoolApp` and show how to [obtain the base path from app settings or other configuration providers](xref:blazor/host-and-deploy/app-base-path#obtain-the-app-base-path-from-configuration).
   * Follow the sub-application configuration guidance in <xref:host-and-deploy/iis/advanced#sub-applications>. The sub-app's folder path under the root site becomes the virtual path of the sub-app. For an app base path of `/CoolApp`, the Blazor app is placed in a folder named `CoolApp` under the root site and the sub-app takes on a virtual path of `/CoolApp`.

diff --git a/aspnetcore/blazor/host-and-deploy/webassembly/azure-static-web-apps.md b/aspnetcore/blazor/host-and-deploy/webassembly/azure-static-web-apps.md
@@ -1,18 +1,18 @@
 ---
-title: Host and deploy ASP.NET Core Blazor WebAssembly with Azure Static Web Apps
+title: Host and deploy ASP.NET Core standalone Blazor WebAssembly with Azure Static Web Apps
 author: guardrex
-description: Learn how to host and deploy Blazor WebAssembly with Microsoft Azure Static Web Apps.
+description: Learn how to host and deploy standalone Blazor WebAssembly with Microsoft Azure Static Web Apps.
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
 ms.date: 03/31/2025
 uid: blazor/host-and-deploy/webassembly/azure-static-web-apps
 ---
-# Host and deploy ASP.NET Core Blazor WebAssembly with Azure Static Web Apps
+# Host and deploy ASP.NET Core standalone Blazor WebAssembly with Azure Static Web Apps
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
-This article explains how to host and deploy Blazor WebAssembly with [Microsoft Azure Static Web Apps](https://azure.microsoft.com/products/app-service/static).
+This article explains how to host and deploy standalone Blazor WebAssembly with [Microsoft Azure Static Web Apps](https://azure.microsoft.com/products/app-service/static).
 
 ## Deploy from Visual Studio
 

diff --git a/aspnetcore/blazor/host-and-deploy/webassembly/azure-storage.md b/aspnetcore/blazor/host-and-deploy/webassembly/azure-storage.md
@@ -1,18 +1,18 @@
 ---
-title: Host and deploy ASP.NET Core Blazor WebAssembly with Azure Storage
+title: Host and deploy ASP.NET Core standalone Blazor WebAssembly with Azure Storage
 author: guardrex
-description: Learn how to host and deploy Blazor WebAssembly using Microsoft Azure Storage.
+description: Learn how to host and deploy standalone Blazor WebAssembly using Microsoft Azure Storage.
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
 ms.date: 03/31/2025
 uid: blazor/host-and-deploy/webassembly/azure-storage
 ---
-# Host and deploy ASP.NET Core Blazor WebAssembly with Azure Storage
+# Host and deploy ASP.NET Core standalone Blazor WebAssembly with Azure Storage
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
-This article explains how to host and deploy Blazor WebAssembly using [Microsoft Azure Storage](/azure/storage/common/storage-introduction).
+This article explains how to host and deploy standalone Blazor WebAssembly using [Microsoft Azure Storage](/azure/storage/common/storage-introduction).
 
 Azure Storage static file hosting allows serverless Blazor app hosting. Custom domain names, the Azure Content Delivery Network (CDN), and HTTPS are supported.