-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
Support for Blazor WASM debugging #44
Comments
I think it just works for Fun.Blazor wasm, you just need to add
into your launchSettings.json. |
Can't get it to work on VS Code though: Here is the Works fine on FsBolero though. |
Are you using mix mode template. If so, it may not work. I only tried pure WASM mode. And only updated pure WASM mode template. And I only tried on VS for Windows. |
Today, I also tried the latest pure WASM template in VSCode, the generated default launch.json is working fine with the debug too: {
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Launch and Debug Standalone Blazor WebAssembly App",
"type": "blazorwasm",
"request": "launch",
"cwd": "${workspaceFolder}"
}
]
} |
@albertwoo FsBolero has support for WebAssembly debugging in VS using Chrome-devtools:
fsbolero/Bolero#294
fsbolero/Bolero#307
Would it be possible to do something similar with Fun.Blazor?
Thanks.
The text was updated successfully, but these errors were encountered: