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

Add support for launching DebugProxy from VS #22589

Closed
captainsafia opened this issue Jun 5, 2020 · 3 comments
Closed

Add support for launching DebugProxy from VS #22589

captainsafia opened this issue Jun 5, 2020 · 3 comments
Assignees
Labels
affected-most This issue impacts most of the customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-debugging This issue is related to debugging of Blazor WebAssembly apps feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly severity-blocking This label is used by an internal tool
Milestone

Comments

@captainsafia
Copy link
Member

To support more debugging scenarios, we need to move the launching of the DebugProxy from our DevServer logic to VS.

Note: for this, we will need some new APIs implemented in VS to support launching a process before starting a debugging session.

@captainsafia captainsafia added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly feature-blazor-debugging This issue is related to debugging of Blazor WebAssembly apps enhancement This issue represents an ask for new feature or an enhancement to an existing one labels Jun 5, 2020
@mkArtakMSFT mkArtakMSFT added this to the Next sprint planning milestone Jun 8, 2020
@ghost
Copy link

ghost commented Aug 10, 2020

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.

@captainsafia captainsafia added affected-most This issue impacts most of the customers severity-blocking This label is used by an internal tool labels Oct 7, 2020
@ghost
Copy link

ghost commented Oct 9, 2020

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
Copy link
Contributor

Closing this - while I still think there's work to be done, I don't think having a piecemeal issue necessarily helps us plan this better.

@ghost ghost locked as resolved and limited conversation to collaborators Nov 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affected-most This issue impacts most of the customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-debugging This issue is related to debugging of Blazor WebAssembly apps feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly severity-blocking This label is used by an internal tool
Projects
None yet
Development

No branches or pull requests

3 participants