Blazor Debug article updates 8.0

[guardrex]

Fixes #30170
Addresses #28161

@wgrs ... This doesn't address everything that we discussed.

We won't document use of the C# Dev Kit until it reaches final release. If you're hitting problems with it, then open an issue at https://github.com/microsoft/vscode-dotnettools/issues (if the problem isn't already there opened by someone else).

For the rest of the scenarios here, the IDE guidance is almost fully working AFAICT. There's one bug with BWA debugging in VSC. The problem isn't that the Counter component in the .Client project couldn't be debugged ... that was fine. It was anything added to the server app. No debugging in the server app works. This problem has been forwarded to the product unit for investigation. I don't know if they're investigating internally or if they opened an issue somewhere.

I had very mixed results with the debugging a Blazor WASM app in the browser. The Firefox guidance worked with some minor tweaks to Dan's blog post guidance, so I'm placing some updates in that section. I flat-out can't get MS Edge debugging to work properly. I can get all the way to the Sources showing the pages and setting a breakpoint (e.g., in the Counter component), but I can't get the breakpoint to hit. Also, I was only even able to get that far when running the app via the .NET CLI, not via VS. Running via VS ended in very cryptic errors and a lot of 😢 trying to figure out what I might be doing wrong ... or if it's just a local machine issue that only affects my (new) PC.

There are a number of updates here to clean up and better organize this topic. It had become messy over the years as we kept touching it with new and updated content.

I'll open a new issue with these follow-up items ...

• Deal with the C# Dev Kit when it comes out.
• Deal with the pieces here that I couldn't get working. I'll reach out to the product unit offline to see when they want to take a look at the two problems I was hitting with MS Edge. I'll get on this immediately (Monday). I also need to ask if the new FF browser debugging works on macOS.
• Follow-up on the BWA server project debugging fix. I think on this one that I'll just check again at RC2 to see if it's fixed.

I'll open the issue right after I merge this.

UPDATE: Issue opened at #30443. I'll get back to work on that on Monday.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/debug.md	Debug ASP.NET Core Blazor WebAssembly
aspnetcore/blazor/tutorials/signalr-blazor.md	[Visual Studio](https://review.learn.microsoft.com/en-us/aspnet/core/blazor/tutorials/signalr-blazor?branch=pr-en-us-30440)