Skip to content

Commit 4b11212

Browse files
authored
Merge pull request #119623 from westdavidr/patch-1
Fix typos (SingalR -> SignalR)
2 parents 3b539c2 + 22c0a73 commit 4b11212

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-signalr/signalr-tutorial-build-blazor-server-chat-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -371,7 +371,7 @@ Beginning in Visual Studio 2019 version 16.2.0, Azure SignalR Service is built i
371371

372372
## Publish to Azure
373373

374-
When you deploy the Blazor app to Azure App Service, we recommend that you use [Azure SignalR Service](/aspnet/core/signalr/scale#azure-signalr-service). Azure SingalR Service allows for scaling up a Blazor Server app to a large number of concurrent SignalR connections. In addition, the SignalR service's global reach and high-performance datacenters significantly aid in reducing latency due to geography.
374+
When you deploy the Blazor app to Azure App Service, we recommend that you use [Azure SignalR Service](/aspnet/core/signalr/scale#azure-signalr-service). Azure SignalR Service allows for scaling up a Blazor Server app to a large number of concurrent SignalR connections. In addition, the SignalR service's global reach and high-performance datacenters significantly aid in reducing latency due to geography.
375375

376376
> [!IMPORTANT]
377377
> In a Blazor Server app, UI states are maintained on the server side, which means a sticky server session is required to preserve state. If there is a single app server, sticky sessions are ensured by design. However, if there are multiple app servers, there are chances that the client negotiation and connection may go to different servers which may lead to an inconsistent UI state management in a Blazor app. Hence, it is recommended to enable sticky server sessions as shown below in *appsettings.json*:
@@ -422,7 +422,7 @@ When you deploy the Blazor app to Azure App Service, we recommend that you use [
422422
dotnet add package Microsoft.Azure.SignalR --version 1.5.1
423423
```
424424
425-
1. Add a call to `AddAzureSingalR()` in `Startup.ConfigureServices()` as demonstrated below.
425+
1. Add a call to `AddAzureSignalR()` in `Startup.ConfigureServices()` as demonstrated below.
426426

427427
```cs
428428
public void ConfigureServices(IServiceCollection services)

0 commit comments

Comments
 (0)