unhandled exception - possibly COM

  • Thread starter Thread starter casey chesnut
  • Start date Start date
C

casey chesnut

from reading past threads, this seems to be a common problem,
but i cannot seem to find a fix ...

i've got a WinForms app that i need to be bulletproof.
right now, it is calling a separate assembly to thumbnail videos.
the thumbnails are being generated through a COM interop call to
IExtractImage.
every once in a while, this fails,
and i get an exception that bubbles up and crashes my application.
that top application usually refers to ole32.dll, which i dont refer to in
my solution.

i've got try / catch everywhere.
i've tried catching COMException explicitly, and also generic catch{}.
i dont see any events that i need to catch in.

would it help if i combined everything into 1 assembly?
what else should i do, other than spawn another process?

Thank you,
casey
http://www.brains-N-brawn.com
 
Some more info ...

i'm already doing UnhandledException on the AppDomain,
and Application.ThreadException before I Run my form.

neither of those catch the Exception.

all that happens is i get the MessageBox that says:

YourApp.exe has encounted a problem and needs to close.
We are sorry for the inconvenience.

Error Signature:
AppName: YourApp.exe AppVer: 1.0.1723.33554 ModName: ole32.dll
ModVer: 5.1.2600.2180 Offset: 000460d0

it is running on .NET 1.1 with SP1.

Thank you,
casey
 
Back
Top