Blazor options configuration 8.0

aspnetcore/blazor/fundamentals/handle-errors.md

@@ -287,6 +287,28 @@ The <xref:Microsoft.AspNetCore.Components.Server.CircuitOptions.DetailedErrors>
 > [!WARNING]
 > Always avoid exposing error information to clients on the Internet, which is a security risk.
 
+:::moniker range=">= aspnetcore-8.0"
+
+## Detailed errors for Razor component server-side rendering
+
+*This section applies to Blazor Web Apps.*
+
+Use the `DetailedErrors` option to control producing detailed information on errors for Razor component server-side rendering. The default value is `false`.
+
+The following example enables detailed errors:
+
+```csharp
+builder.Services.AddRazorComponents(options => options.DetailedErrors = true);
+```
+
+<!-- UPDATE 8.0 We need to flesh out this warning with the consequences
+                of enabling detailed errors in production. -->
+
+> [!WARNING]
+> Only enable detailed errors in the Development environment.
+
+:::moniker-end
+
 ## Manage unhandled exceptions in developer code
 
 For an app to continue after an error, the app must have error handling logic. Later sections of this article describe potential sources of unhandled exceptions.

aspnetcore/blazor/fundamentals/signalr.md

@@ -279,6 +279,32 @@ services.AddServerSideBlazor().AddHubOptions(options =>
 
 For information on memory management, see <xref:blazor/host-and-deploy/server#memory-management>.
 
+## Blazor hub options
+
+Configure <xref:Microsoft.AspNetCore.Builder.ComponentEndpointRouteBuilderExtensions.MapBlazorHub%2A> options to control <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions> of the Blazor hub:
+
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.CloseOnAuthenticationExpiration>
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.TransportMaxBufferSize>
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.ApplicationMaxBufferSize>
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.TransportSendTimeout>
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.AllowStatefulReconnects>
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.AuthorizationData> (*Read only*)
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.LongPolling> (*Read only*)
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.MinimumProtocolVersion>
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.Transports>
+* <xref:Microsoft.AspNetCore.Http.Connections.HttpConnectionDispatcherOptions.WebSockets> (*Read only*)
+
+In the following example, options are set to their default values. Place the call to `app.MapBlazorHub` after the call to `app.MapRazorComponents` in the app's `Program` file.
+
+```csharp
+app.MapBlazorHub(options =>
+{
+    options.{OPTION} = {VALUE};
+});
+```
+
+In the preceding example, the `{OPTION}` placeholder is the option, and the `{VALUE}` placeholder is the value.
+
 ## Maximum receive message size
 
 *This section only applies to projects that implement SignalR.*

aspnetcore/blazor/fundamentals/static-files.md

@@ -48,9 +48,33 @@ if (builder.Environment.IsStaging())
 }
 ```
 
-## Static web asset base path
+:::moniker range=">= aspnetcore-8.0"
+
+## Prefix for Blazor WebAssembly assets
+
+*This section applies to Blazor Web Apps.*
+
+Use the `PathPrefix` endpoint option to gets or set the path string that indicates the prefix for Blazor WebAssembly assets. The path must correspond to a referenced Blazor WebAssembly application project.
+
+```csharp
+endpoints.MapRazorComponents<App>()
+    .AddInteractiveWebAssemblyRenderMode(options => 
+        options.PathPrefix = "{PATH PREFIX}");
+```
 
-<!-- UPDATE 8.0 TBD if the content is correct for >=8.0 -->
+In the preceding example, the `{PATH PREFIX}` placeholder is the path prefix and must start with a forward slash (`/`).
+
+In the following example, the path prefix is set to `/path-prefix`:
+
+```csharp
+endpoints.MapRazorComponents<App>()
+    .AddInteractiveWebAssemblyRenderMode(options => 
+        options.PathPrefix = "/path-prefix");
+```
+
+:::moniker-end
+
+## Static web asset base path
 
 :::moniker range=">= aspnetcore-8.0"
 

aspnetcore/blazor/security/server/index.md

@@ -691,6 +691,24 @@ Two additional abstractions participate in managing authentication state:
 
 [!INCLUDE[](~/includes/aspnetcore-repo-ref-source-links.md)]
 
+:::moniker range=">= aspnetcore-8.0"
+
+## Temporary redirection URL validity duration
+
+*This section applies to Blazor Web Apps.*
+
+Use the `TemporaryRedirectionUrlValidityDuration` option to get or set the lifetime of data protection validity for temporary redirection URLs emitted by Blazor server-side rendering. These are only used transiently, so the lifetime only needs to be long enough for a client to receive the URL and begin navigation to it. However, it should also be long enough to allow for clock skew across servers. The default value is five minutes.
+
+In the following example the value is extended to seven minutes:
+
+```csharp
+builder.Services.AddRazorComponents(options => 
+    options.TemporaryRedirectionUrlValidityDuration = 
+        TimeSpan.FromMinutes(7));
+```
+
+:::moniker-end
+
 ## Additional resources
 
 * [Quickstart: Add sign-in with Microsoft to an ASP.NET Core web app](/azure/active-directory/develop/quickstart-v2-aspnet-core-webapp)

aspnetcore/migration/70-80.md

@@ -80,10 +80,11 @@ The following migration scenarios are covered:
 * [Adopt Blazor Web App conventions](#adopt-blazor-web-app-conventions)
 * [Convert a Blazor Server app into a Blazor Web App](#convert-a-blazor-server-app-into-a-blazor-web-app)
 * [Convert a hosted Blazor WebAssembly app into a Blazor Web App](#convert-a-hosted-blazor-webassembly-app-into-a-blazor-web-app)
+* [Update service and endpoint option configuration](#update-service-and-endpoint-option-configuration)
 
 For guidance on adding Blazor support to an ASP.NET Core app, see <xref:blazor/components/integration#add-blazor-support-to-an-aspnet-core-app>.
 
-## Adopt Blazor Web App conventions
+### Adopt Blazor Web App conventions
 
 To optionally adopt all of the new Blazor Web App conventions, we recommend the following process:
 
@@ -388,6 +389,27 @@ Blazor WebAssembly apps are supported in .NET 8 without any code changes. Use th
 
    If using the .NET CLI, run the project from the `Server` project's folder.
 
+### Update service and endpoint option configuration
+
+With the release of Blazor Web Apps in .NET 8, Blazor service and endpoint option configuration is updated with the introduction of new API for interactive component services and component endpoint configuration.
+
+Updated configuration guidance appears in the following locations:
+
+* [Server-side circuit handler options](xref:blazor/fundamentals/signalr?view=aspnetcore-8.0&preserve-view=true#server-side-circuit-handler-options): Covers new Blazor-SignalR circuit and hub options configuration.
+* [Render Razor components from JavaScript](xref:blazor/components/js-spa-frameworks?view=aspnetcore-8.0&preserve-view=true#render-razor-components-from-javascript): Covers dynamic component registration with <xref:Microsoft.AspNetCore.Components.Web.JSComponentConfigurationExtensions.RegisterForJavaScript%2A>.
+* [Blazor custom elements: Blazor Web App registration](xref:blazor/components/js-spa-frameworks?view=aspnetcore-8.0&preserve-view=true#blazor-web-app-registration): Covers root component custom element registration with `RegisterCustomElement`.
+* [Prefix for Blazor WebAssembly assets](xref:blazor/fundamentals/static-files?view=aspnetcore-8.0&preserve-view=true#prefix-for-blazor-webassembly-assets): Covers control of the path string that indicates the prefix for Blazor WebAssembly assets.
+* [Temporary redirection URL validity duration](xref:blazor/security/server/index?view=aspnetcore-8.0&preserve-view=true#temporary-redirection-url-validity-duration): Covers control of the lifetime of data protection validity for temporary redirection URLs emitted by Blazor server-side rendering.
+* [Detailed errors](xref:blazor/fundamentals/handle-errors?view=aspnetcore-8.0&preserve-view=true#detailed-errors-for-razor-component-server-side-rendering): Covers enabling detailed errors for Razor component server-side rendering.
+* [Prerendering configuration](xref:blazor/components/render-modes?view=aspnetcore-8.0&preserve-view=true#prerendering): Prerendering is enabled by default for Blazor Web Apps. Follow this link for guidance on how to disable prerendering if you have special circumstances that require an app to disable prerendering.
+
+<!-- UPDATE 8.0 HOLD until the Forms node PR merges
+                https://github.com/dotnet/AspNetCore.Docs/pull/30834
+
+* [Form binding options](xref:blazor/forms/binding?view=aspnetcore-8.0&preserve-view=true#additional-binding-options): Covers form binding options configuration.
+
+-->
+
 ## Update Docker images
 
 For apps using Docker, update your *Dockerfile* `FROM` statements and scripts. Use a base image that includes the ASP.NET Core 8.0 runtime. Consider the following `docker pull` command difference between ASP.NET Core 7.0 and 8.0: