Hi, We use CruiseControl.NET to automate testing of our C++ application. When our application fails, sometimes it will present a crash dialog box. This is bad because effectively the automated build process is hung until CruiseControl.NET times out the build and kills the executable. This occurs regardless of whether a user is logged in to the machine.
These dialogs are not of our own doing. Some come from the debug CRT (e.g. abort()) and others are the usual crash dialog presented by the OS. Is there a way to suppress all crash dialogs on our autobuild machine so that all failure modes of a C++ application result in a timely reporting of failure? (Rather than waiting for the build timeout to be reached.) Sever failure modes of a C++ application cause this dialog problem for us: Throw uncaught C++ exception. Call abort(). Dereference NULL. Call __debugbreak(). -- Paul Richards
