AspNetCore.Docs/aspnetcore/host-and-deploy/blazor/server-side.md

2.3 KiB

title author description monikerRange ms.author ms.custom ms.date uid
Host and deploy ASP.NET Core Blazor server-side guardrex Learn how to host and deploy a Blazor server-side app using ASP.NET Core. >= aspnetcore-3.0 riande mvc 09/05/2019 host-and-deploy/blazor/server-side

Host and deploy Blazor server-side

By Luke Latham, Rainer Stropek, and Daniel Roth

Host configuration values

Server-side apps that use the server-side hosting model can accept Generic Host configuration values.

Deployment

With the server-side hosting model, Blazor is executed on the server from within an ASP.NET Core app. UI updates, event handling, and JavaScript calls are handled over a SignalR connection.

A web server capable of hosting an ASP.NET Core app is required. Visual Studio includes the Blazor Server App project template (blazorserverside template when using the dotnet new command).

Connection scale out

Blazor server-side apps require one active SignalR connection for each user. A production Blazor server-side deployment requires a solution for supporting as many concurrent connections as required by the app. The Azure SignalR Service handles the scaling of connections and is recommended as a scaling solution for Blazor server-side apps. For more information, see xref:signalr/publish-to-azure-web-app.

SignalR configuration

SignalR is configured by ASP.NET Core for the most common Blazor server-side scenarios. For custom and advanced scenarios, consult the SignalR articles in the Additional resources section.

Additional resources