we currently have an application with 2 pdfviewers for document comparison. Unfortunately, there are some pdf files causing exceptions either at loading them into the viewer or when being rendered by the viewer. The exception comes from within a 3rd party control.
So we tried to solve some of those problems by binding to AppDomain.CurrentDomain.FirstChanceException. When such an exception is thrown, a message should be shown in the viewer having the problem.
For we can at time current not distinguish from firstchanceexception's arguments which viewer has a problem, the message is shown in both viewers, even in the one who could have displayed his document without issues.
So the question is:
Is there any way to find the source of the exception?
sender is targeting towards application.run, not very helpful.
FirstChanceExceptionEventArgs are targeting at a type used by our viewer-controls, but without any indication which one has triggered the exception.