Update Blazor WebAssembly debugging limitations

[danroth27]

Description

In the .NET 7 docs and earlier doc versions the Blazor WebAssembly debugging docs has a section that says "Unsupported scenarios for Blazor WebAssembly apps include:", but as far as I can tell, everything listed is actually supported. It looks like this was already fixed for the .NET 8 docs, but not the earlier doc sets.

Also, in the limitations section:

Limitation	Status	Addressed in
Break on unhandled exceptions.	The debugger can break on unhandled exceptions, but Blazor currently catches all exceptions so they are all handled (see #42510). The workaround is to break when the exception is thrown. I think we should remove this item as a limitation and add a note about how to debug exceptions.	.NET 6
Hit breakpoints during app startup before the debug proxy is running. This includes breakpoints in the Program file and breakpoints in the OnInitialized{Async} lifecycle methods of components that are loaded by the first page requested from the app.	This is no longer a limitation	.NET 6
Debug in non-local scenarios (for example, Windows Subsystem for Linux (WSL) or Visual Studio Codespaces).	I think these scenarios are still unsupported. @thaysg?	TBD
Use a symbol server for debugging.	Addressed in .NET 8	.NET 8

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/debug?view=aspnetcore-7.0&tabs=visual-studio

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/debug.md

Document ID

4d06e565-282d-6387-aa90-cb2c2986d35a

Article author

guardrex