wrote in message
ups.com...
Hi,
If such a crash occurs, i want to handle it.
I think we may not be able to handle all crash scenarios for Addins as
they reside inside Outlook.
So i wanted to handle it programatically to enable my Addin.

They occur inside of Outlooks address space, but they are likely caused by
your AddIn's failure to release everything it has referenced and/or
allocated.

I usually add a call to OutputDebugString in each of the AddIn's shut-down
event handlers, and run a debugging port listener to monitor it. You should
see OnBeginShutdown, OnDisconnection and Terminate fire; if any of them
don't, your code has failed to release something, and that's what's causing
Outlook to crash, and that's why Outlook fingers your code as the culprit,
and disables it.

Ask yourself: does Outlook crash if my AddIn is not installed?.

If the answer is 'yes' then remove any other AddIns to eliminate them as
source of the problem, and if it still crashes with no AddIns, reinstall
Office, or do whatever else it takes to get Outlook stable all by itself
before continuing your project -- because trying to develop and test
software in a corrupted environment is just plain dumb.

If the answer is 'no' that should tell you something important, that you've
obviously overlooked, and are now attempting to discount...

So I'll spell it out for you once again: your AddIn is causing Outlook to
crash, because it's not releasing everthing it's using, and thus failing to
shut down correctly. Fix that problem, and Outlook will cease to crash.

-Mark




Thanks
Balaji