Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve cross-links in Blazor server-side host doc #12732

Merged
merged 5 commits into from
Jun 26, 2019
Merged

Improve cross-links in Blazor server-side host doc #12732

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
035179f
Improve cross-links in Blazor server-side host doc
guardrex Jun 6, 2019
f9c33cb
React to feedback
guardrex Jun 11, 2019
360d2d9
Additional updates
guardrex Jun 11, 2019
6f0e642
React to feedback
guardrex Jun 12, 2019
bce94fe
Add tech name to topic title
guardrex Jun 14, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions aspnetcore/host-and-deploy/blazor/server-side.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
title: Host and deploy Blazor server-side
title: Host and deploy ASP.NET Core Blazor server-side
author: guardrex
description: Learn how to host and deploy a Blazor server-side app using ASP.NET Core.
monikerRange: '>= aspnetcore-3.0'
ms.author: riande
ms.custom: mvc
ms.date: 04/26/2019
ms.date: 06/11/2019
uid: host-and-deploy/blazor/server-side
---
# Host and deploy Blazor server-side
Expand All @@ -22,19 +22,19 @@ With the [server-side hosting model](xref:blazor/hosting-models#server-side), Bl

A web server capable of hosting an ASP.NET Core app is required. Visual Studio includes the **Blazor (server-side)** project template (`blazorserverside` template when using the [dotnet new](/dotnet/core/tools/dotnet-new) command).

<!--
## Connection scale out

**INSERT: Concerns are the same as publishing an ASP.NET Core SignalR app**
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](/azure/azure-signalr/) 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>.

**INSERT: Content on the Azure SignalR Service**
## SignalR configuration

**INSERT: Manually turn on WebSockets support**

-->
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](#additional-resources) section.

## Additional resources

* <xref:signalr/introduction>
* [Azure SignalR Service Documentation](/azure/azure-signalr/)
* [Quickstart: Create a chat room by using SignalR Service](/azure/azure-signalr/signalr-quickstart-dotnet-core)
* <xref:host-and-deploy/index>
* <xref:tutorials/publish-to-azure-webapp-using-vs>
* [Deploy ASP.NET Core preview release to Azure App Service](xref:host-and-deploy/azure-apps/index#deploy-aspnet-core-preview-release-to-azure-app-service)