Add support for launching DebugProxy from blazorwasm debug type in VS Code

[captainsafia]

To support debugging in WSL and Codespaces, we need to move the logic that launches the DebugProxy in Blazor from our DevServer logic to the blazorwasm debug type.

To fully support remote debugging, there is some work required to add support for using a WebSocket-based transport when communicating with the browser launched over the users machine. This will be tracked in a separate issue at #29657.

[mkArtakMSFT]

@captainsafia moving these debugging related issues to RC1 but we need to re-evaluate together which ones will make it in.

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[MarkusRodler]

It would be nice to mention this constraint in the docs: https://docs.microsoft.com/de-de/aspnet/core/blazor/debug?view=aspnetcore-5.0&tabs=visual-studio-code

[captainsafia]

cc: @guardrex Let's add a quick note in the Blazor WASM debugging docs that it currently only works for local scenarios.

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.