Another good way is to simply enter the statement that the debugger starts. In our code, all of our fixtures are based on some simple custom basic fixtures with some utilities in them, such as | debug |
this statement simply launches the debugger as follows:
public void Debug() { System.Diagnostics.Debugger.Launch(); }
as soon as the statement is applied, the debugger starts.
this has the advantage that you can quickly put it wherever you want. Sometimes you may have a long test that uses the same statements over and over, in which case this is good, because you can do it right before that problem.
ryber
source share