[2005] COM (Domino Objects) Crashing Application when Uncaught Exception Encountered

[visualAd]

I know uncaught exceptions are meant to crash the application. However, when I run the application in debug mode an uncaught exception causes the application to crash.

I am using the Lotus Notes Domino objects COM. I have concluded that during normal operation the API can perform an normal clean-up and termination of the objects but and exception causes prevents this from happening.

Is there any way of manually releasing and disposing of a COM object? Has anyone else used the Domino API before?

This is really annoying me because I cannot see the exception details. Instead I just get the standard "do you want to send an error report dialog box". This makes the application an absolute pain to debug during development.

[Craig Gemmill]

Did you try using structured error handling to encompass all of the COM calls? It's possible that it is raising an error; you're just not handling it. Or maybe the COM object has an error handling delegate or something.

If you did try that, then it means the error is not being raised to the calling assembly... so there is little you can do to correct the situation.

You can release most objects by calling .Dispose() or setting all references to =nothing.
http://msdn2.microsoft.com/en-us/lib...k6(VS.71).aspx