You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/platforms/how-to-use-web-assembly.md
+18-11
Original file line number
Diff line number
Diff line change
@@ -46,33 +46,40 @@ cd BrowserTest.Browser
46
46
dotnet run
47
47
48
48
# Output:
49
-
# App url: http://localhost:5000/index.html
50
-
# App url: https://localhost:5001/index.html
49
+
# App url: http://127.0.0.1:53576/
50
+
# App url: https://127.0.0.1:53577/
51
+
# Debug at url: http://127.0.0.1:53576/_framework/debug
52
+
# Debug at url: https://127.0.0.1:53577/_framework/debug
51
53
```
52
54
53
-
54
55
### Deployment
55
56
In the `BrowserTest.Browser` directory, run:
56
57
```bash
57
58
dotnet publish
58
-
59
-
# ... (build output)
60
-
# Generated app bundle at .../bin/Release/net8.0/browser-wasm/AppBundle/
61
59
```
62
-
Now you can serve your app from the `bin/Release/net8.0/browser-wasm/AppBundle` folder (for .NET 8.0, for example) using your favorite web server (such as Azure Static Web Apps).
63
60
64
-
> **Beware:**
61
+
After project was published, .NET SDK creates an app bundle directory with `index.html` file and compiled application files.
62
+
With latest .NET 8 SDK, this directory is located at `bin/Release/net8.0-browser/browser-wasm/publish`.
63
+
Now you can serve your app from this directory using your favorite web server (such as Azure Static Web Apps).
64
+
65
+
:::note
66
+
On older .NET SDK versions, app bundle was located in different directory: `bin/Release/net8.0-browser/browser-wasm/AppBundle` (search for `AppBundle`).
67
+
:::
68
+
69
+
:::warning
65
70
Currently using `dotnet publish` with the `-o` or `--output` flag does not produce the AppBundle folder in the output directory. (See [this issue](https://github.com/dotnet/runtime/issues/94319).) You'll still have to grab it out of the `bin` directory at the path specified by the publish output.
71
+
:::
66
72
67
73
#### Testing AppBundle locally
68
-
You can serve your wasm app from the AppBundle directly using the [dotnet-serve](https://github.com/natemcmaster/dotnet-serve) tool as follows:
74
+
75
+
You can serve your wasm app from this directly using the [dotnet-serve](https://github.com/natemcmaster/dotnet-serve) tool as follows:
0 commit comments