We’re attempting to update our application in order to submit it for Vista certification. Part of the requirements are to handle only known exceptions and have Windows Error Reporting deal with all unhandled exceptions.
We have a global exception handler in our application (subscribed to the Application.ThreadException event) and in there, we perform certain processing for known exceptions, but if an exception is unknown we wish to throw it out for the app to terminate and WER to handle.
We cannot see a way of doing this and maintaining the call stack if we re-throw then the call stack is recreated.
We’ve looked at terminating via Environment.FailFast() but we don’t believe that that gives the exception information we’d require.
Are we missing something obvious?
Why not just throw a new exception and set the InnerException property to be the unhandled one? The default StackTrace property will concatenate both traces together.
Bear in mind that if you’re debugging from a memory dump that you’ve retrieved from WinQual then it’ll be a native exception that’s trapped anyway. It’s almost always possible to walk back up the native stack and retrieve the managed exception and if you have symbols available it’s usually easy to find out what went wrong. The stack trace of the managed exception will be redundant in this situation anyway.