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

Update source of the blazor.server.js script #12374

Merged
merged 2 commits into from
May 10, 2019
Merged

Update source of the blazor.server.js script #12374

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8421d83
Update source of the blazor.server.js script
guardrex May 10, 2019
e1012b0
React to feedback
guardrex May 10, 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
4 changes: 2 additions & 2 deletions aspnetcore/blazor/hosting-models.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: Understand client-side and server-side Blazor hosting models.
monikerRange: '>= aspnetcore-3.0'
ms.author: riande
ms.custom: mvc
ms.date: 04/25/2019
ms.date: 05/10/2019
uid: blazor/hosting-models
---
# Blazor hosting models
Expand Down Expand Up @@ -78,7 +78,7 @@ There are downsides to server-side hosting:
* Reduced scalability: The server must manage multiple client connections and handle client state.
* An ASP.NET Core server is required to serve the app. Deployment without a server (for example, from a CDN) isn't possible.

†The *blazor.server.js* script is published to the following path: *bin/{Debug|Release}/{TARGET FRAMEWORK}/publish/{APPLICATION NAME}.App/dist/_framework*.
†The *blazor.server.js* script is served from an embedded resource in the ASP.NET Core shared framework.

### Reconnection to the same server

Expand Down