Document/implement solutions for supporting debugging in in-browser experience

[captainsafia]

With the work we are doing to move launching the debug proxy to the IDE, we need to provide solutions for users who want to debug using the in-browser experience. So far, we have two options for this:

• Users can add an invocation to our UseWebAssemblyDebugging middleware in their host server.
• Users can launch the debug proxy host themselves.

Another alternative we can consider is launching the debug proxy host when the user runs dotnet run.

The first two options already exist and will just need documentation.

Depending on timing, we might be able to add support for the third option (requires a code change).

[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.

[pranavkm]

Thanks for contacting us. We're closing this issue as there was no community involvement here for quite a while now.

You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.