[wasm] Improve experience of debugging library tests

[radical]

The current state leaves a lot to be desired.

• Accurate documentation is missing on how to do this ILONA
• dotnet run --project ../tests.csproj .. doesn't work as it seems to pick the wrong WasmAppHost, and AppBundle path. ILONA
• When running the app with --debug on codespaces, the web server is started on localhost:5000, but chrome fails to connect to this - 403 . It does connect to 127.0.0.1:5000 though. Investigate, and fix.
• If debugging is not enabled for the tests, it isn't indicated well, and can be really confusing for the user to not see any source files
• When the runtime is built for Release, - check and warn about any missing pdbs
• And check that this works correctly, automatically, for Debug config
• Handle page refreshes, reconnects better
• host: For the browser, if the console is not being forwarded, then the app should not try to connect to the web socket, and host shouldn't be listening on that either.

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The current state leaves a lot to be desired.

• dotnet run --project ../tests.csproj .. doesn't work as it seems to pick the wrong WasmAppHost, and AppBundle path.
• When running the app with --debug on codespaces, the web server is started on localhost:5000, but chrome fails to connect to this - 403 . It does connect to 127.0.0.1:5000 though. Investigate, and fix.
• If debugging is not enabled for the tests, it isn't indicated well, and can be really confusing for the user to not see any source files
• When the runtime is built for Release, - check and warn about any missing pdbs
• And check that this works correctly, automatically, for Debug config
• Handle page refreshes, reconnects better
• host: For the browser, if the console is not being forwarded, then the app should not try to connect to the web socket, and host shouldn't be listening on that either.

Author:	radical
Assignees:	-
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The current state leaves a lot to be desired.

• dotnet run --project ../tests.csproj .. doesn't work as it seems to pick the wrong WasmAppHost, and AppBundle path.
• When running the app with --debug on codespaces, the web server is started on localhost:5000, but chrome fails to connect to this - 403 . It does connect to 127.0.0.1:5000 though. Investigate, and fix.
• If debugging is not enabled for the tests, it isn't indicated well, and can be really confusing for the user to not see any source files
• When the runtime is built for Release, - check and warn about any missing pdbs
• And check that this works correctly, automatically, for Debug config
• Handle page refreshes, reconnects better
• host: For the browser, if the console is not being forwarded, then the app should not try to connect to the web socket, and host shouldn't be listening on that either.

Author:	radical
Assignees:	-
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-

[lewing]

cc @thaystg @ilonatommy

[radical]

Individual items can be picked up to work on.

[radical]

And just write your name after the item, if you are working on it.