Sure, we must avoid catching and attempting to handle AccessViolationExceptions(AVEs). However, in my current case, the exception is thrown from a COM+ managed component which terminates the process that threw the exception, therefore, cleaning up correctly. However, a windows service, hosting WCF, that consumes said COM+ component receives the bubbled up AVE causing the service crash.
The IErrorHandlers in place don’t seem to fire/detect AVEs.
Is there any way to enable WCF IErrorHandlers to catch AVEs?
It is not possible for IErrorHandlers to catch exceptions similar to AccessViolationExceptions (SEHExceptions).