History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RSRP-63583
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Ilya Ryzhenkov
Reporter: Andrew Serebryansky
Votes: 1
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
ReSharper

Extend the exception handling in Visual Studio debugger

Created: 03 Apr 08 11:37   Updated: 09 Apr 08 16:25
Component/s: VS integration
Fix Version/s: Future Versions
Security Level: Everybody (All jira users)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Duplicate
 
This issue is duplicated by:
RSRP-63223 On exception, simplify exception igno... Normal Closed


 Description  « Hide
Would it be possible to extend the exception handler in the debugger so it would offer to uncheck or not include that exception. So if you break on exception, you could run into some exception type that you don't want to break on and simply remove that from break on exception.

MS's debugger exception editor is pretty poor.

Another approach would be a way to save selected exception. Sometimes I need to turn off break on exception, and when I do that, I loose all me exception settings when everything is unchecked,



 All   Comments   Work Log   Change History      Sort Order:
Ilya Ryzhenkov - 09 Apr 08 16:06
Do you mean changing Debug | Exceptions checkboxes in some other way? I didn't quite understand the request.

Mark Famous - 09 Apr 08 16:19
Then debugging, and you break on an unhandled exception, and the exception catcher pops up, enhance that popup so there is an option to remove the check box from the exception type. If you do that, and continue running and that exception were to come up again, you would not break.

Secondary to that (and probably somewhat unrelated) was some sort of mechanism for saving selected exceptions in the Debug | Exceptions dialog as a named set - so you can reload it later. Currently, if you want to break on any exception and check the top level box in the tree, all exceptions are checked and you loose any defined settings where you had certain exceptions selected. If you could save a named set, then you could temporarily set to break on all exceptions, but then load in your predefined set later.

Example: I turn off break on SocketException because my client socket is disconnected when I'm debugging. The socket connection is maintained on a background thread and is not part of what I'm debugging. Trouble is, if I reset the Debug | Exceptions dialog to not break on any exceptions, but then want to go back to breaking on exceptions, I have to weed down through the tree and uncheck SocketException (again).


Ilya Ryzhenkov - 09 Apr 08 16:25
This is not something we are going to do in ReSharper in the near future, but sometime we can reconsider this. Thanks for suggestion.