If your addins crashes Outlook, or gets blamed for crashing Outlook there's
nothing you can do to prevent it from being disabled.
There are cases where some other addin or automation code might crash
Outlook or crash the VB runtime, and just because your addin is VB6 it will
be blamed, and there's nothing you can do.
One such case was (possibly still is) Apple's ITunes synching software. It
tried to use the Outlook object model from a background thread, which will
crash or hang Outlook. Due to how the stack is implemented that ended up
having Outlook blame any VB6 addin for the crash, as the first place it
happens is from the VB6 runtime.
In cases like that you need to know every other addin the user is running.
Have them disable all of them and see if the problem goes away. Then
re-enable them one at a time until the problem comes back (assuming only 1
badly written addin of course) and that's the problem one. You still need to
ensure that you aren't leaving any exceptions unhandled.
One other thing that may occur is exceptions from system dll's such as
kernel32.dll or ntdll.dll. Sometimes those can be fired by WordMail or other
out of process code and you won't even get an exception bubble up to you.
For those you need to isolate the cause and try to figure out how you're
causing the exception.
"yves pion" <hotline@socetem.fr> wrote in message
news:u4y58Ii$KHA.5044@TK2MSFTNGP04.phx.gbl...
> Hello,
> I have developped a ComAddin for olk2003 in VB6.
> the ComAddin is activated each time Outlook starts.
> For many days, the comaddin works fine, but sometimes for a unknown
> reason, it is deactivated (found in outlook 'deactivated component' ).
> I have handled all errors inside my Comaddin , so i cannot understand why
> i could be deactivated.
> Is there a solution to keep the comaddin always activated ?
> Thanks in advance.
>
