Blazor webassembly debugger doesn't stop on exception

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:It's more difficult to complete my work]
When debugging any dotnet application in VS we can choose to stop on any exception. That make the debugging really quick when there are exceptions and we want to inspect what happened.

However, when debugging a Blazor Webassemby application, that doesn't happen. You get an error and you need to find the place where the error happened and set a break point and hope it breaks there.

Same behaviour should be expected from Blazor Webassemby apps to make development easier.

Steps:
1 - Createa Webassembly app
2 - do something that creates an exception
3 - Start in Debug mode and in the Exception Settings dialog select to stop on all CLR exceptions
4 - Expected: VS stops then the Exception happens
What happens: Nothing. You get an error in the browser and need to inspect the console for errors.

---

Original Comments

Feedback Bot on 3/16/2021, 07:33 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

[mkArtakMSFT]

@lewing FYI

[ghost]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This issue has been moved from a ticket on Developer Community.

---

[severity:It's more difficult to complete my work]
When debugging any dotnet application in VS we can choose to stop on any exception. That make the debugging really quick when there are exceptions and we want to inspect what happened.

However, when debugging a Blazor Webassemby application, that doesn't happen. You get an error and you need to find the place where the error happened and set a break point and hope it breaks there.

Same behaviour should be expected from Blazor Webassemby apps to make development easier.

Steps:
1 - Createa Webassembly app
2 - do something that creates an exception
3 - Start in Debug mode and in the Exception Settings dialog select to stop on all CLR exceptions
4 - Expected: VS stops then the Exception happens
What happens: Nothing. You get an error in the browser and need to inspect the console for errors.

---

Original Comments

Feedback Bot on 3/16/2021, 07:33 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

Author:	vsfeedback
Assignees:	-
Labels:	area-Diagnostics-coreclr, untriaged
Milestone:	-

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This issue has been moved from a ticket on Developer Community.

---

[severity:It's more difficult to complete my work]
When debugging any dotnet application in VS we can choose to stop on any exception. That make the debugging really quick when there are exceptions and we want to inspect what happened.

However, when debugging a Blazor Webassemby application, that doesn't happen. You get an error and you need to find the place where the error happened and set a break point and hope it breaks there.

Same behaviour should be expected from Blazor Webassemby apps to make development easier.

Steps:
1 - Createa Webassembly app
2 - do something that creates an exception
3 - Start in Debug mode and in the Exception Settings dialog select to stop on all CLR exceptions
4 - Expected: VS stops then the Exception happens
What happens: Nothing. You get an error in the browser and need to inspect the console for errors.

---

Original Comments

Feedback Bot on 3/16/2021, 07:33 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

Author:	vsfeedback
Assignees:	-
Labels:	area-Debugger-mono, area-Diagnostics-coreclr, untriaged
Milestone:	-

[lewing]

this should be fixed with #54040