[wasm][debugger] Side effect of setting fixed debuggerProxy port

[ilonatommy]

Description

Cannot debug the debuggerProxy because it's using the same port (9300) as my sample Blazor application.

Reproduction Steps

Start debugging the debuggerProxy in VS by attaching a Blazor sample app to the debuggerProxy process:

1. Copy files from artefacts/bin/BrowserDebugHost/Debug of our main branch into Server/bin/Debug/net6.0/BlazorDebugProxy of a fresh dotnet 6 Blazor app.
2. Open Blazor project in VS and start debugging.
3. Open DebuggerProxy project in VS and start debugging.

Expected behavior

It should find any other port and start, so that we could attach Blazor project to it and debug.

Actual behavior

Exception:

because Blazor is running already on 9300.

Regression?

Yes, by c26475c.

Known Workarounds

Changing DevToolsProxyPort value manually.

Configuration

No response

Other information

No response

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

Issue Details

---

Description

Cannot debug the debuggerProxy because it's using the same port (9300) as my sample Blazor application.

Reproduction Steps

Start debugging the debuggerProxy in VS by attaching a Blazor sample app to the debuggerProxy process:

1. Copy files from artefacts/bin/BrowserDebugHost/Debug of our main branch into Server/bin/Debug/net6.0/BlazorDebugProxy of a fresh dotnet 6 Blazor app.
2. Open Blazor project in VS and start debugging.
3. Open DebuggerProxy project in VS and start debugging.

Expected behavior

It should find any other port, start there so that we could attach Blazor project to it and debug.

Actual behavior

Exception:

because Blazor is running already on 9300.

Regression?

Yes, by c26475c.

Known Workarounds

No response

Configuration

No response

Other information

No response

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