Another common thing we often see in usability studies are
cases where developers set breakpoints, run the application, try out some
input, hit a breakpoint, and manually check if some condition is true before
deciding to investigate further. If the scenario doesn’t match what they
are after, they press F5 to continue the app, try out some other input, and
repeat the process manually.
Visual Studio’s conditional breakpoint capability provides a
much, much easier way to handle this. Conditional breakpoints allow you to
break in the debugger only if some specific condition that you specify is
met. They help you avoid having to manually inspect/resume your application,
and can make the whole debugging process a lot less manual and tedious.