> I usually also add a handler for unhandled exceptions this way:
>
> AppDomain.CurrentDomain.UnhandledException += new
> UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);
>
> private static void CurrentDomain_UnhandledException(object sender,
> UnhandledExceptionEventArgs e)
> {
> }
>
> One thing to look at is if those users with problems are running any code
> that integrates with and starts Outlook with no UI (no Explorers or
> Inspectors). Some applications that do that include synching software that
> synchs with PDA's, IPods or IPhones, etc. That's also called "headless"
> mode.
>
> The earlier versions of the VSTO runtime terminated the addin if Outlook was
> started in headless mode, a fix for that was made in the latest version of
> the VSTO runtime. Make sure your users have the latest VSTO runtime, and see
> if what I mentioned applies to any of them.
>
> --
> Ken Slovak
> [MVP - Outlook]
>
http://www.slovaktech.com> Author: Professional Programming Outlook 2007.
> Reminder Manager, Extended Reminders, Attachment Options.
>
http://www.slovaktech.com/products.htm>
>
> "rob_tt08" <robtt08[ at ]discussions.microsoft.com> wrote in message
> news:296D3229-35E6-4D24-9ED1-C43B24374E50[ at ]microsoft.com...
> > Ken,
> >
> > The addin installs and loads successfully and works at first but sometimes
> > when the user starts Outlook at a later date the addin does not start and
> > needs to be re-enabled.
> >
> > Users have not reported anything out of the ordinary immediately prior to
> > experiencing this problem so we are unsure of its cause. I will follow
> > your
> > advice and add more exception handling (using the
> > System.Windows.Forms.Application.ThreadException event) in case there are
> > still unhandled exceptions, and see if the problem is reported again.
> >
> > Outlook has sometimes crashed during ordinary use for these users but the
> > addin was not disabled after this. The error handling code which we are
> > already using (try/catch blocks around the code in the event handlers and
> > methods of our addin) did not catch or log any errors on these occaisions.
> >
> > Will the ThreadException event catch all possible errors or is it possible
> > that the addin could be causing problems for Outlook which make it
> > unstable
> > without actually throwing an exception?
> >
> > Thank you for your advice.
>
>