Microsoft Visual Studio .NET usage recommendations

| > The Unit Test Framework > Usage recomendations > Microsoft Visual Studio .NET users specific |

#### Microsoft Visual Studio .NET usage recommendations

Use custom build step to automatically start test program after compilation
If you got fatal exception somewhere within test case, make debugger break at the point the failure by adding extra command line argument

| Use custom build step to automatically start test program after compilation

I found it most convenient to put test program execution as a post-build step in compilation. To do so use project property page:

Full command you need in "Command Line" field is:

`"$(TargetDir)\$(TargetName).exe"` --result_code=no --report_level=no

Note that both report level and result code are suppressed. This way the only output you may see from this command are possible runtime errors. But the best part is that you could jump through these errors using usual keyboard shortcuts/mouse clicks you use for compilation error analysis:

| If you got fatal exception somewhere within test case, make debugger break at the point the failure by adding extra command line argument
| If you got "memory access violation" message (or any other message indication fatal or system error) when you run you test, to get more information of error location add --catch_system_errors=no to the test run command line: Now run the test again under debugger and it will break at the point of failure.