Add support for launching DebugProxy from VS #22589
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
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.
The text was updated successfully, but these errors were encountered: