An improved debugging experience for Blazor WebAssembly apps

[Rick-Anderson]

@guardrex I couldn't find a dup. Do you own this?

author: daroth
Data types shown in the debugger now match the expected .NET data types. - Type members and member visibility use expected icons. - The displayed call stack is cleaned up to only shows the .NET call stack and correctly honors the Just My Code setting. - The modules window is now supported. - Expression evaluation support in the Immediate window and for watches and conditional breakpoints is expanded and improved. To enable the new debugging experience simply update your Blazor app to target .NET 9.

Internal only: blazor-wasm-debugger-improvements

[guardrex]

I'll check on this; but because we mostly don't document tooling features, we might not be covering these ... they're just things that now work that didn't work before.

[Rick-Anderson]

I'll check on this; but because we mostly don't document tooling features, we might not be covering these ... they're just things that now work that didn't work before.

Maybe @ghogen is responsible and you review it?

[guardrex]

I doubt it. Usually, absent tooling features just catch up in the background without any fanfare. If we had to say that something wasn't working, that gets called out. That's why I need to check those items to confirm that we didn't say anything about a broken/missing feature. Even if I don't find any doc changes to make, I can drop these remarks into the Migration article just to surface them.

[guardrex]

I checked ... we're good here 👍. No changes to the coverage are required because these features failing to work in the past weren't covered by the article. Closing now.