M
Michael E. Pouliot
The documentation for Control.BeginInvoke states "Exceptions within the
delegate method are considered untrapped and will be sent to the
application's untrapped exception handler". However, other articles
reference the fact that Control.EndInvoke will marshal an Exception back to
the caller. Upon attempting this, it appears that both are true. The
Exception is marshaled back, but an Unhandled Exception is also raised.
Furthermore, I cannot seem to catch the Unhandled Exception by implementing
handlers for either Application.ThreadException or
AppDomain.UnhandledException.
Optimally, I would want the runtime to not generate an Unhandled Exception,
since it appears to marshal the Exception just fine. Has anyone else dealt
with this issue?
Thanks,
MP
delegate method are considered untrapped and will be sent to the
application's untrapped exception handler". However, other articles
reference the fact that Control.EndInvoke will marshal an Exception back to
the caller. Upon attempting this, it appears that both are true. The
Exception is marshaled back, but an Unhandled Exception is also raised.
Furthermore, I cannot seem to catch the Unhandled Exception by implementing
handlers for either Application.ThreadException or
AppDomain.UnhandledException.
Optimally, I would want the runtime to not generate an Unhandled Exception,
since it appears to marshal the Exception just fine. Has anyone else dealt
with this issue?
Thanks,
MP