Re: ThisApplication_Startup event not firing
- From: "Ken Slovak - [MVP - Outlook]" <kenslovak@xxxxxxxx>
- Date: Wed, 20 Dec 2006 16:40:44 -0500
Disabled items are stored in the registry under a Resiliency key but each disabled addin is noted by a randomly generated value so you can't tell which is which.
Normally, an unshimmed .NET addin (shared addin) shares its AppDomain with all other unshimmed addins. If one gets disabled they all do. However, VSTO sets up it's own shim replacement and has its own AppDomain for each of its addins, so that's not a problem with VSTO.
Are you sure this is a VSTO addin and not a shared COM addin? If you crashed Outlook with a previous incarnation of the same VSTO addin I could see it being disabled, but otherwise not.
--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm
"Bon733" <bon@xxxxxxxxxxxxxxxxxxxx> wrote in message news:7A208423-606F-4BA2-B543-9F072DEDCF7F@xxxxxxxxxxxxxxxx
Thanks. I just found the problem. For some reason under Help\About\Disabled
Items in Outlook, a previous add-in was selected as disabled. Once I enabled
the add-in, all the remaining add-ins\tests worked as expected in debug mode.
Why would disabling one add-in disable all future add-ins from running? Is
the a setting or an ID that this feature is using to disbale add-ins?
.
- References:
- ThisApplication_Startup event not firing
- From: Bon733
- Re: ThisApplication_Startup event not firing
- From: Ken Slovak - [MVP - Outlook]
- Re: ThisApplication_Startup event not firing
- From: Bon733
- ThisApplication_Startup event not firing
- Prev by Date: Re: ThisApplication_Startup event not firing
- Next by Date: Re: problem deploy VSTO2005SE application
- Previous by thread: Re: ThisApplication_Startup event not firing
- Index(es):
Relevant Pages
|