daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Hosted WASM app start update (#23227)

pull/23228/head
Luke Latham 2021-09-07 13:54:34 -05:00 committed by GitHub
parent 69fc5139c2
commit ebef4aaef8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 15 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
aspnetcore/blazor/debug.md
View File

@ -83,7 +83,7 @@ The placeholder values for the WebSockets protocol (`wsProtocol`), host (`url.ho
To debug a Blazor WebAssembly app in Visual Studio:
1. Create a new hosted Blazor WebAssembly solution.
1. Press <kbd>F5</kbd> to run the app in the debugger.
1. With the **`Server`** project selected in **Solution Explorer**, press <kbd>F5</kbd> to run the app in the debugger.
> [!NOTE]
> **Start Without Debugging** (<kbd>Ctrl</kbd>+<kbd>F5</kbd>) isn't supported. When the app is run in Debug configuration, debugging overhead always results in a small performance reduction.
@ -189,7 +189,7 @@ For information on configuring VS Code assets in the `.vscode` folder, see the *
For guidance on configuring VS Code assets in the `.vscode` folder and where to place the `.vscode` folder in the solution, see the **Linux** operating system guidance in <xref:blazor/tooling?pivots=linux>.
The `.vscode/launch.json` file sets the current working directory to the `**Server**` project's folder, typically `Server` for a hosted Blazor WebAssembly solution:
The `.vscode/launch.json` file sets the current working directory to the **`Server`** project's folder, typically `Server` for a hosted Blazor WebAssembly solution:
```json
"cwd": "${workspaceFolder}/Server"
@ -201,7 +201,7 @@ If Microsoft Edge is used for debugging instead of Google Chrome, the `.vscode/l
"browser": "edge"
```
The `.vscode/tasks.json` file adds the **`Server`** app's project file path to the `dotnet build` arguments under `args`. The `**Server**` project's folder is typically named `Server` in a solution based on the hosted Blazor WebAssembly project template. The following example uses the project file for the **`Server`** app of the [Blazor-SignalR tutorial](xref:tutorials/signalr-blazor)), which has a project file named `BlazorWebAssemblySignalRApp.Server.csproj`:
The `.vscode/tasks.json` file adds the **`Server`** app's project file path to the `dotnet build` arguments under `args`. The **`Server`** project's folder is typically named `Server` in a solution based on the hosted Blazor WebAssembly project template. The following example uses the project file for the **`Server`** app of the [Blazor-SignalR tutorial](xref:tutorials/signalr-blazor)), which has a project file named `BlazorWebAssemblySignalRApp.Server.csproj`:
```json
{
@ -506,7 +506,7 @@ The placeholder values for the WebSockets protocol (`wsProtocol`), host (`url.ho
To debug a Blazor WebAssembly app in Visual Studio:
1. Create a new hosted Blazor WebAssembly solution.
1. Press <kbd>F5</kbd> to run the app in the debugger.
1. With the **`Server`** project selected in **Solution Explorer**, press <kbd>F5</kbd> to run the app in the debugger.
> [!NOTE]
> **Start Without Debugging** (<kbd>Ctrl</kbd>+<kbd>F5</kbd>) isn't supported. When the app is run in Debug configuration, debugging overhead always results in a small performance reduction.
@ -612,7 +612,7 @@ For information on configuring VS Code assets in the `.vscode` folder, see the *
For guidance on configuring VS Code assets in the `.vscode` folder and where to place the `.vscode` folder in the solution, see the **Linux** operating system guidance in <xref:blazor/tooling?pivots=linux>.
The `.vscode/launch.json` file sets the current working directory to the `**Server**` project's folder, typically `Server` for a hosted Blazor WebAssembly solution:
The `.vscode/launch.json` file sets the current working directory to the **`Server`** project's folder, typically `Server` for a hosted Blazor WebAssembly solution:
```json
"cwd": "${workspaceFolder}/Server"
@ -624,7 +624,7 @@ If Microsoft Edge is used for debugging instead of Google Chrome, the `.vscode/l
"browser": "edge"
```
The `.vscode/tasks.json` file adds the **`Server`** app's project file path to the `dotnet build` arguments under `args`. The `**Server**` project's folder is typically named `Server` in a solution based on the hosted Blazor WebAssembly project template. The following example uses the project file for the **`Server`** app of the [Blazor-SignalR tutorial](xref:tutorials/signalr-blazor)), which has a project file named `BlazorWebAssemblySignalRApp.Server.csproj`:
The `.vscode/tasks.json` file adds the **`Server`** app's project file path to the `dotnet build` arguments under `args`. The **`Server`** project's folder is typically named `Server` in a solution based on the hosted Blazor WebAssembly project template. The following example uses the project file for the **`Server`** app of the [Blazor-SignalR tutorial](xref:tutorials/signalr-blazor)), which has a project file named `BlazorWebAssemblySignalRApp.Server.csproj`:
```json
{
@ -929,7 +929,7 @@ The placeholder values for the WebSockets protocol (`wsProtocol`), host (`url.ho
To debug a Blazor WebAssembly app in Visual Studio:
1. Create a new hosted Blazor WebAssembly solution.
1. Press <kbd>F5</kbd> to run the app in the debugger.
1. With the **`Server`** project selected in **Solution Explorer**, press <kbd>F5</kbd> to run the app in the debugger.
> [!NOTE]
> **Start Without Debugging** (<kbd>Ctrl</kbd>+<kbd>F5</kbd>) isn't supported. When the app is run in Debug configuration, debugging overhead always results in a small performance reduction.
@ -1035,7 +1035,7 @@ For information on configuring VS Code assets in the `.vscode` folder, see the *
For guidance on configuring VS Code assets in the `.vscode` folder and where to place the `.vscode` folder in the solution, see the **Linux** operating system guidance in <xref:blazor/tooling?pivots=linux>.
The `.vscode/launch.json` file sets the current working directory to the `**Server**` project's folder, typically `Server` for a hosted Blazor WebAssembly solution:
The `.vscode/launch.json` file sets the current working directory to the **`Server`** project's folder, typically `Server` for a hosted Blazor WebAssembly solution:
```json
"cwd": "${workspaceFolder}/Server"
@ -1047,7 +1047,7 @@ If Microsoft Edge is used for debugging instead of Google Chrome, the `.vscode/l
"browser": "edge"
```
The `.vscode/tasks.json` file adds the **`Server`** app's project file path to the `dotnet build` arguments under `args`. The `**Server**` project's folder is typically named `Server` in a solution based on the hosted Blazor WebAssembly project template. The following example uses the project file for the **`Server`** app of the [Blazor-SignalR tutorial](xref:tutorials/signalr-blazor)), which has a project file named `BlazorWebAssemblySignalRApp.Server.csproj`:
The `.vscode/tasks.json` file adds the **`Server`** app's project file path to the `dotnet build` arguments under `args`. The **`Server`** project's folder is typically named `Server` in a solution based on the hosted Blazor WebAssembly project template. The following example uses the project file for the **`Server`** app of the [Blazor-SignalR tutorial](xref:tutorials/signalr-blazor)), which has a project file named `BlazorWebAssemblySignalRApp.Server.csproj`:
```json
{

6
aspnetcore/blazor/tooling.md
View File

@ -30,6 +30,8 @@ zone_pivot_groups: operating-systems
1. Press <kbd>Ctrl</kbd>+<kbd>F5</kbd> to run the app.
When running a hosted Blazor WebAssembly solution in Visual Studio, the startup project of the solution is the **`Server`** project.
For more information on trusting the ASP.NET Core HTTPS development certificate, see <xref:security/enforcing-ssl#trust-the-aspnet-core-https-development-certificate-on-windows-and-macos>.
When executing a hosted Blazor WebAssembly app, run the app from the solution's **`Server`** project.
@ -287,6 +289,8 @@ For Blazor WebAssembly apps, only method body replacement is currently supported
1. Press <kbd>Ctrl</kbd>+<kbd>F5</kbd> to run the app.
When running a hosted Blazor WebAssembly solution in Visual Studio, the startup project of the solution is the **`Server`** project.
For more information on trusting the ASP.NET Core HTTPS development certificate, see <xref:security/enforcing-ssl#trust-the-aspnet-core-https-development-certificate-on-windows-and-macos>.
When executing a hosted Blazor WebAssembly app, run the app from the solution's **`Server`** project.
@ -515,6 +519,8 @@ dotnet new blazorserver -h
1. Press <kbd>Ctrl</kbd>+<kbd>F5</kbd> to run the app.
When running a hosted Blazor WebAssembly solution in Visual Studio, the startup project of the solution is the **`Server`** project.
For more information on trusting the ASP.NET Core HTTPS development certificate, see <xref:security/enforcing-ssl#trust-the-aspnet-core-https-development-certificate-on-windows-and-macos>.
When executing a hosted Blazor WebAssembly app, run the app from the solution's **`Server`** project.