Hi,
currently i'm developing with VSTO 2005 ans VS 2005 Team Suite for Office Outlook 2003.
I wrote an Add-In with C# and it works well, creating a setup which grants the CAS too.
But today i changed some code within, rebuild the solution and tried to start a debug session with a break point right in the ThisApplication.ThisApplication_Startup Method. And nothing happens!!
My Add-In was not loaded anymore.
I tried to do a reinstall with one of the previous generated setup packages (which worked!) and started Outlook manually.
And nothing happens. My Add-In was not loaded.
So, even previous versions which worked yesterday doesn' work anymore. In fact, MS VSTO samples for Outlook Add-Ins doesn't work either. They worked yesterday too!
The Add-Ins show up in the COM-Add-Ins List in Outlook, but can't get checked. They can get checked but after clicking OK and then returning to the dialog they remain unchecked. There is no error message below.
So it seems to me that the AddinLoader.dll can't load them anymore. But why CAS should be granted, especially in debugging sessions.
I cleaned the registry from my addin, done a restart of the pc, but nothing changes this behaviour.
Any Ideas
Best Regards,
Manuel

Outlook: no Add-In does load anymore
Joakim Gyllstedt
There are several possibilities as to why your add-in doens't load anymore:
Li Wang
Hello,
I think Sven's response is on the right track. If your add-in does something unexpected at startup, then Outlook can disable your add-in from loading in the future. It sounds in your case like Outlook has "hard disabled" your add-in, in which case all Outlook add-ins that use AddinLoader.dll are prevented from loading.
The following topics in the VSTO 2005 documentation provide more information about why your add-in might have been disabled by Outlook, and how to re-enable it:
- Debugging in Outlook Projects (http://msdn2.microsoft.com/en-us/library/ms269003(VS.80).aspx)
- How to: Re-enable an Outlook Add-in That Has Been Disabled (http://msdn2.microsoft.com/en-us/library/ms268871(VS.80).aspx)
I hope this helps,
McLean Schofield