I am working on an application that continuously opens IE, performs a task, closes it and then repeats. However in the event that IE crashes during execution the system is prepared to continue onto the next iteration however the error report remains open and does not allow the process to fully close. This means that it continues to occupy memory until a user clicks the dialog box saying to ignore the error.
Currently there are two solutions that I am looking at, the use of VectoredExceptionHandlers, and the ability to completely disable WER.
My understanding of VectoredExceptionHandlers is that they will intercept any exception thrown by my application and deal with them before they make it to WER. However since the crash is actually occurring in the IE process that my application started I am not sure if these handlers would still be able to prevent WER from receiving the exception.
I also do not wish to disable WER completely on the system as the other questions on StackOverflow suggest, I only want it disabled while my application is running.
Does anyone have any more knowledge into these options or a better way to handle this?
The WER Settings page from MSDN might be what you want to take a look at at. There’s a section in the registry for excluded applications. And there seems to be this WerAddExcludedApplication function you can call. Judging by the page on Vectored Exception Handling, it’s probably not going to help you catching exceptions from a different application.