Skip to content

Add support for launching DebugProxy from blazorwasm debug type in VS Code #22587

@captainsafia

Description

@captainsafia

To support debugging in WSL and Codespaces, we need to move the logic that launches the DebugProxy in Blazor from our DevServer logic to the blazorwasm debug type.

To fully support remote debugging, there is some work required to add support for using a WebSocket-based transport when communicating with the browser launched over the users machine. This will be tracked in a separate issue at #29657.

Metadata

Metadata

Assignees

Labels

DoneThis issue has been fixedUser StoryA single user-facing feature. Can be grouped under an epic.affected-mediumThis issue impacts approximately half of our customersarea-blazorIncludes: Blazor, Razor ComponentsenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-blazor-debuggingThis issue is related to debugging of Blazor WebAssembly appsfeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyseverity-blockingThis label is used by an internal tool

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions