Launching Blazor debugging proxy from UI extension#22683
Conversation
|
|
||
| * Break on unhandled exceptions. | ||
| * Hit breakpoints during app startup before the debug proxy is running. This includes breakpoints in `Program.Main` (`Program.cs`) and breakpoints in the [`OnInitialized{Async}` lifecycle methods](xref:blazor/components/lifecycle#component-initialization-oninitializedasync) of components that are loaded by the first page requested from the app. | ||
| * Debug in non-local scenarios (for example, [Windows Subsystem for Linux (WSL)](/windows/wsl/) or [Visual Studio Codespaces](/visualstudio/codespaces/overview/what-is-vsonline)). |
There was a problem hiding this comment.
We don't support debugging remotely in Visual Studio yet.
Also, there's a bug that prevents the WSL/VS Code scenario from working fully so I would omit this for now.
There was a problem hiding this comment.
😕 ... That's a bit confusing. I can't grok what "yet" and "for now" mean WRT today versus at GA. We can leave it if at GA things will work and this content will be accurate at that time.
The lead-in for this list is For now, you can't:. I assumed from the PU PR that as of 6.0, one can ...
Debug in non-local scenarios (for example, [Windows Subsystem for Linux (WSL)](/windows/wsl/) or [Visual Studio Codespaces](/visualstudio/codespaces/overview/what-is-vsonline)).
Therefore, this line will only appear in content for <6.0.
If I still fail to grasp what's changing, you'll have to explain it out a bit more.
... or I suppose you could edit the PR directly to make it right. It might be faster than trying to explain.
There was a problem hiding this comment.
Yeah, sorry for the confusion.
I assumed from the PU PR that as of 6.0, one can .
Nope this is not true. We can basically close this PR.
Context: we pushed the change to support remote debugging in .NET 6 Preview 1. It worked for a while then a downstream component changes their API in .NET 6 Preview 3 and it has be broken since then. There are no plans to fix for .NET 6 at the moment.
There was a problem hiding this comment.
Ah ... gotcha ... and I'll note this on the 6.0 tracking issue as well.
2 participants
Fixes #22443
Addresses #22045
Looks like we just need to version out the line that we added earlier ...
Note that the whole list must be versioned: This docs feature will 💥 if you try to do it on a single listitem.
Is there anything else for docs to cover Add support for launching DebugProxy from blazorwasm debug type in VS Code (dotnet/aspnetcore #22587)?