Better exception handing so that VS won't be crushed
Please improve stability/exception handling, provide optional "Submit crash report" window so that we can feedback the exception and other details, and isolate NCrunch from the VS.
We have been seeing unstable behaviour caused by NCrunch while intensively running 1000+ tests across dozens server nodes, all of them cause VS restarted.
That's extremely annoying giving the fact that after the VS crash NCrunch "tries" to pick up tests from the very beginning. We can't complete the whole test suite having crashed somewhere along the way.
NCrunch is already militant with its error handling and separation from VS. A big feature introduced early this year was the ability to run the engine outside the VS process (enabled by default through the 'Engine hosting strategy' global configuration setting).
At the moment the only known way in which NCrunch can cause the VS process to crash is through resource utilisation. Have you been able to exact any useful information about the crashes when these appear? Does devenv.exe spike in memory utilisation? Is there any chance of getting a stack trace when the process goes down?