WASM debug scenario update

[guardrex]

Fixes #30824

For adding a note about how to debug exceptions, is the guidance what Thays provided at ...

• Break on first-chance exception in Web Assembly debugger aspnetcore#42510 (comment)
• Break on first-chance exception in Web Assembly debugger aspnetcore#42510 (comment)

... what we're passing on? My plan is to place a section on it, which I've started but haven't finished yet. UPDATE: I've made the PR say what I think it's supposed to say.

BTW, I'm not sure what Thays took a screenshot of for that. Where is that "All Exceptions" setting? ... and note that her text remark doesn't exactly match what's shown in the screenshot. Nevermind! I found it. I haven't looked at that UI in several years ... Debug > Windows > Exception Settings. I thought it would be in Options.

UPDATE: I've tried it here, and it doesn't seem to work. I'm setting ...

No 🎲🎲 ... still just breaks in the browser with the stack trace without the debugger indicating that anything has happened. I'm using the code from the issue that throws on a button click ...

<p>
    <button @onclick="ThrowException">Throw Exception</button>
</p>

@code {
    public void ThrowException()
    {
        throw new Exception("throwing new ex");
    }
}

... and I tried the Counter component approach ...

private void IncrementCount()
{
    currentCount++;

    if (currentCount == 3)
    {
        throw new Exception("throwing new ex");
    }
}

cc: @thaystg

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/debug.md	Debug ASP.NET Core apps

[guardrex]

@Thays ... If the guidance here is correct in the new Break on unhandled exceptions section, I can't get it to work. All I get is the dev tools console logging of the error and stack trace. Nothing happens in the debugger. Any idea what I'm not doing correctly? ... or are these instructions incomplete?

[thaystg]

I have just tested.
Started the app, enabled the exceptions, clicked in the "Click me" button.

[thaystg]

[guardrex]

🐀🍔 Roasted Rat Burgers! 🐀🍔

😆 ... well ... it's not working here. It must be a local problem for ME 🦖. The guidance on the PR is correct, so I'm going to go ahead and merge it. I'll check again on this after RTM, when I'll be moving off of Preview VS back to normal release VS. Perhaps, something is funky with my Preview VS install.

Ok ... I just made a tracking note to check again with release VS in 24Q1.