DragDrop event called as a result of COM drag and drop operation and is
called directly by COM. If any exception should happen they are probably
re-routed to the caller (which is not your application) and it looks like
they get swallowed.

Signature
HTH
Stoitcho Goutsev (100)
> In the simplified code below, shouldn't the thrown exception cause the app
> to terminate since it is unhandled? It doesn't seem to do anything in
[quoted text clipped - 41 lines]
> }
> }
sb - 11 Jul 2006 22:41 GMT
Thanks for the reply but what does this have to do with COM? I thought
drag/drop events were just normal windows messages (ie WM_DROPFILES). I'll
have to look into that some more I guess. The wierd part is that if I wrap
the exception in a try/catch block within the Form.DragDrop event, I can
intercept it just like any other exception. I thought another thread might
be handling the exception but the ManagedThreadID within the method is the
same as the rest of the application.
I would like to understand this issue better...I just don't get it :)
-sb
> DragDrop event called as a result of COM drag and drop operation and is
> called directly by COM. If any exception should happen they are probably
[quoted text clipped - 46 lines]
>> }
>> }