7 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Andrew Skalkin commented  ·  July 25, 2012 11:08 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Can anyone tell me if they implemented this feature in VS2012?

• petriashev commented  ·  June 19, 2012 6:20 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I want to ignore exceptions in logger config style (with wildchars):
  ignore: System.IO.*
  MyNamespace.Subsystem.*
  *FileNotFound*

• Philippe commented  ·  March 31, 2012 6:29 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  It would also be nice to have an option to have finer grained control so that it would be possible to ignore an exception at a specific location (user code, specific function, specific DLL) as some generic exceptions like null pointers might get thrown at many locations but a few should be ignored.

  Also a way to temporarily enable or disabled all exceptions (or load/save exceptions settings) would be nice.

  An option to ignore the exception for this debugging session would also be nice.

  Debugging attributes might also be useful so that once could mark code at function or class level with something like [DebuggerStopOnException(false)] and it should apply by default to any function called by the function on whioch the attribute was added.

• Andrew Skalkin commented  ·  March 9, 2012 8:15 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  The absence of that feature, combined with the fact that .NET throws and handles exception in non-exceptional situations (such as FileNotFound when the corresponding *.XmlSerializers.dll assembly has not been pre-built), drives me nuts for the past 10 years. I am aware that I can set it up to break on my code only, but that doesn't help much. I would also suggest to make exception management more powerful, such as adding the ability to suppress a particular exception on a particular stack trace, etc.

• IgbyD commented  ·  January 13, 2012 2:15 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  YES PLEASE! Put a checkbox on the exception dialog that disabled "break on thrown" for the current exception.

• RobertWG commented  ·  August 22, 2011 12:22 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This would save me a whole lot of annoying SocketExceptions from background threads while debugging.

• Richard Beier commented  ·  July 22, 2011 11:20 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Great idea. This would help me get past Unity's frequent SynchronizationLockExceptions...