Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to set port for browser refresh websocket connection when using dotnet watch #39765

Open
JulesImmerzeel opened this issue Jan 23, 2022 · 4 comments
Labels
area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-dotnetwatch This issue is related to the dotnet-watch command-line tool (now external) Pillar: Dev Experience triaged

Comments

@JulesImmerzeel
Copy link

Is your feature request related to a problem? Please describe.

I am trying to use docker when working with dotnet. Currently when I use dotnet watch a websocket connection is created for browser refresh, but the port is randomly assigned. Because of this I can't set the port in my dockerfile and thus can't use auto refresh in browser.

Describe the solution you'd like

A way to set the ports for browser refresh. Perhaps in the launch settings as an optional setting. And still assign a random port if no preference is provided.

@mkArtakMSFT mkArtakMSFT transferred this issue from dotnet/sdk Jan 25, 2022
@mkArtakMSFT mkArtakMSFT added area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI feature-dotnetwatch This issue is related to the dotnet-watch command-line tool (now external) enhancement This issue represents an ask for new feature or an enhancement to an existing one labels Jan 25, 2022
@mkArtakMSFT mkArtakMSFT added this to the Backlog milestone Feb 1, 2022
@ghost
Copy link

ghost commented Feb 1, 2022

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.

@lxsedov
Copy link

lxsedov commented Oct 6, 2023

@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, .NET 9 Planning Dec 15, 2023
@ghost
Copy link

ghost commented Dec 15, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 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.

@danroth27 danroth27 changed the title Dotnet watch ability to set port for browser refresh websocket connection Ability to set port for browser refresh websocket connection when using dotnet watch Jan 30, 2024
@DaveBagler
Copy link

A feature like this would be very valuable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-dotnetwatch This issue is related to the dotnet-watch command-line tool (now external) Pillar: Dev Experience triaged
Projects
None yet
Development

No branches or pull requests

4 participants