0
Planned - Long term

Add a breakpoint in every catch statement

Tony Henrich 6 years ago updated by Omer Raviv (CTO) 6 years ago 0
This is similar to adding a breakpoint in every member. Add one to every catch statement because at times I don't know where the exception.happened and handled. I don't have a good logging capability in every catch.  Useful in aspx pages with lots of event handlers.

Answer

Answer
Planned - Long term
Thanks for the request, Tony! We do have plans to better visualize what exceptions occurred and the flow they went through the various catch blocks.  In case you're not aware, please note you can toggle "Break on all CLR Exceptions" via the OzCode Menu or Toolbar to automatically break whenever an exception is thrown. Then, if you hit F10 repeatedly, you will wind up in the catch block. At any point in this process, you can use the "Show Exception Details" QuickAction and then use the "Go to where exception was thrown" link to get back to the exception's origin.
Planned - Long term
Thanks for the request, Tony! We do have plans to better visualize  about what exceptions occurred and the flow they went through the various catch blocks.  In case you're not aware, please note you can toggle "Break on all CLR Exceptions" via the OzCode Menu or Toolbar to automatically break whenever an exception is thrown. Then, if you hit F10 repeatedly, you will wind up in the catch block. At any point in this process, you can use the "Show Exception Details" QuickAction and then use the "Go to where exception was thrown" link to get back to the exception's origin.
Answer
Planned - Long term
Thanks for the request, Tony! We do have plans to better visualize what exceptions occurred and the flow they went through the various catch blocks.  In case you're not aware, please note you can toggle "Break on all CLR Exceptions" via the OzCode Menu or Toolbar to automatically break whenever an exception is thrown. Then, if you hit F10 repeatedly, you will wind up in the catch block. At any point in this process, you can use the "Show Exception Details" QuickAction and then use the "Go to where exception was thrown" link to get back to the exception's origin.