Skip to content

Launching Blazor debugging proxy from UI extension #22683

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

Closed
guardrex wants to merge 1 commit into from
Closed

Launching Blazor debugging proxy from UI extension #22683

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions aspnetcore/blazor/debug.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,23 @@ Available scenarios include:

For now, you *can't*:

::: moniker range=">= aspnetcore-6.0"

* 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.
* Automatically rebuild the backend `*Server*` app of a hosted Blazor WebAssembly solution during debugging, for example by running the app with [`dotnet watch run`](xref:tutorials/dotnet-watch).

::: moniker-end

::: moniker range="< aspnetcore-6.0"

* 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)).
Copy link
Copy Markdown
Contributor

@captainsafia captainsafia Jul 12, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator Author

@guardrex guardrex Jul 12, 2021 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😕 ... 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.

Copy link
Copy Markdown
Contributor

@captainsafia captainsafia Jul 12, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator Author

@guardrex guardrex Jul 12, 2021 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ... gotcha ... and I'll note this on the 6.0 tracking issue as well.

* Automatically rebuild the backend `*Server*` app of a hosted Blazor WebAssembly solution during debugging, for example by running the app with [`dotnet watch run`](xref:tutorials/dotnet-watch).

::: moniker-end

## Prerequisites

Debugging requires either of the following browsers:
Expand Down