Could anybody tell about how IE handles uncaught exceptions in a hosted
winforms user control? We are having some issues in our app where the
hosted control appears to completely kill IE with no message or debug
info (see
http://groups-beta.google.com/group/microsoft.public.dotnet.framework/browse_frm
/thread/e547f253aa6a20b5/9fd0da14e439e7f1?q=embedded+control+paint+thread&rnum=1
#9fd0da14e439e7f1)
for a similar problem.
It would be useful to know a bit more about what goes on under the hood
so we can prevent this from happening but info seems scarce!
Kind regards,
Will Holley
Technical Manager
Bluewire Technologies Ltd
[MSFT] - 04 May 2005 06:59 GMT
You can take a look at following article to see if it can help:
http://msdn.microsoft.com/msdnmag/issues/02/01/UserCtrl/default.aspx
For the exception in your app, I suggest you may attach VS.NET to a IE
process and debug it to see what code cause such an exception. When you
close a IE windows, your winform control also need to release all resource,
the problem may occur here.
Luke