dotnet watch WebSockets port configuration for HotReload

[sdykae]

From https://github.com/dotnet/sdk/blob/1cbb60f4ad1a34415a8f360c90e92a70587bdb1b/src/BuiltInTools/BrowserRefresh/BrowserScriptMiddleware.cs#L49

We should configure static ports like this.

{
    "SuperHeroAPI": {
      "commandName": "Project",
      "dotnetRunMessages": true,
      "launchBrowser": true,
      "hotReloadEnabled": true,
      "hotReloadProfile": "aspnetcore",
      "launchUrl": "swagger",
      "applicationUrl": "https://localhost:7078;http://localhost:5055",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development",
        "ASPNETCORE_AUTO_RELOAD_WS_ENDPOINT": "wss://localhost:35871,ws://localhost:33863"
      }
    }

Then If you are a vscode remote developer you could just open those ports

[sdykae]

Since
https://github.com/dotnet/sdk/blob/1cbb60f4ad1a34415a8f360c90e92a70587bdb1b/src/BuiltInTools/dotnet-watch/Filters/BrowserRefreshServer.cs#L49

There is no way to configure ws wss urls, ports for dotnet watch, Web client are configurable but server ones are random

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[jrmoreno1]

What determines whether Hot Reloads uses ws or wss?

[lonix1]

Did you find a workaround? Hot reload is unusable as it chooses a random port each time.

[asm-flairstech]

It would be impossible to configure this with CspOptions ConnectSources custom sources for trusted domains if ports are always generated randomly!

[asm-flairstech]

Also the domain doesn't have to be localhost, it could be something else

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

[Trystan-SA]

The year is 2023, and Microsoft still hasn't added an environment variable to prevent its random WebSocket port allocation... 🤦‍♂️

[mkArtakMSFT]

Closing as a dupe of #39765

[sdykae]

@mkArtakMSFT you are closing in favor of a resent issue? why? that is the dupe not this one