I've often used conditional breakpoints that only halt execution under certain conditions but recently I discovered a (presumably old) feature in Visual Studio; the ability to print random things from variables when breakpoints are hit rather than halting execution.
Right-clicking the breakpoint and choosing "When Hit..." brings up this nifty window:
If you combine that feature with the Reflector plugin you can even set breakpoints in 3rd party assemblies and print their variables to make debugging easier!
I've penned down a blog post on this.
ReplyDeletehttps://gobeyondsyllabus.wordpress.com/2015/02/09/use-visual-studio-tracepoints-instead/