Skip to content

Move debug proxy to external process #19702

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.

Sign up for GitHub

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

Jump to bottom
Closed
SteveSandersonMS opened this issue Mar 9, 2020 · 1 comment
Closed

Move debug proxy to external process #19702

SteveSandersonMS opened this issue Mar 9, 2020 · 1 comment
Assignees
@SteveSandersonMS
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Milestone
blazor-wasm-3.2-p...

Comments

@SteveSandersonMS
Copy link
Member

This is needed so that parts of the JS debugger inside VS can work. Currently, the debug proxy runs in-proc within the server being debugged, so if the .NET debugger pauses the server (as it does when "pause all processes" is enabled, which it is by default), this prevents the client debugger from working.
@SteveSandersonMS SteveSandersonMS added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Mar 9, 2020
@mkArtakMSFT mkArtakMSFT added this to the blazor-wasm-3.2-preview3 milestone Mar 9, 2020
@SteveSandersonMS SteveSandersonMS mentioned this issue Mar 11, 2020
Merged
@SteveSandersonMS SteveSandersonMS added Done This issue has been fixed and removed Working labels Mar 13, 2020
@SteveSandersonMS
Copy link
Member Author

Done in #19767

@ghost ghost locked as resolved and limited conversation to collaborators Apr 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@SteveSandersonMS SteveSandersonMS

Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Projects
None yet
Milestone
blazor-wasm-3.2-preview3
Development

No branches or pull requests
2 participants
@SteveSandersonMS @mkArtakMSFT