Don’t stop debugger at THAT exception when it’s thrown and caught

by

DebuggerHidden is your friend!

The common language runtime attaches no semantics to this attribute. It is provided for use by source code debuggers. For example, the Visual Studio 2005 debugger does not stop in a method marked with this attribute and does not allow a breakpoint to be set in the method. Other debugger attributes recognized by the Visual Studio 2005 debugger are the DebuggerNonUserCodeAttribute and the DebuggerStepThroughAttribute.

Tested on VS2010 and works great.

While DebuggerStepThrough seems to also work for some specific debugger versions, DebuggerHidden seems to work for a wider range of situations based on the comments to both answers.

Note that both options do not currently work with iterator block methods or for async/await methods. This could be fixed in a later update of Visual Studio.

Note that it does not work with combination of .NET Core + Rider, you can vote the issue.

More Related Contents:

  1. Put WPF control into a Windows Forms Form?
  2. How do I remedy “The breakpoint will not currently be hit. No symbols have been loaded for this document.” warning?
  3. LINQ query on a DataTable
  4. How can I convert an integer into its verbal representation?
  5. Performance differences between debug and release builds
  6. How to start WinForm app minimized to tray?
  7. How to set session timeout in web.config
  8. Workaround for lack of ‘nameof’ operator in C# for type-safe databinding?
  9. Metadata file ‘.dll’ could not be found
  10. Cannot step into .NET framework source code
  11. String escape into XML
  12. Application.Exit
  13. Generic base class for WinForm UserControl
  14. How can I embed an application manifest into an application using VS2008?
  15. Software rendering mode – WPF
  16. Request.UrlReferrer null?
  17. Unable to connect to ASP.Net Development Server issue
  18. Determine list of event handlers bound to event
  19. User Activity Logging, Telemetry (and Variables in Global Exception Handlers)
  20. Cannot find .cs files for debugging .NET source code
  21. Resolving extension methods/LINQ ambiguity
  22. LOH fragmentation – 2015 update
  23. How can I include line numbers in a stack trace without a pdb?
  24. How can I get “Copy to Output Directory” to work with Unit Tests?
  25. Visual Studio 2015 RTM – Debugging not working
  26. Will #if RELEASE work like #if DEBUG does in C#?
  27. How do I compile my App.config into my exe in a VS2010 C# console app?
  28. Does PowerShell compile scripts?
  29. Get first element from a dictionary
  30. How to check if process is not responding?

Leave a Comment