VSTO Add-In stopped working

[thomas.schager]

Hi,

after a successful testing period, my Outlook 2007 Add-In (VSTO 2005
SE, VS 2005, XP Pro)
stopped working today. The Add-In is not "active" any more, Outlook
does not execute the
Add-In code.

I applied the steps as described in [1] - repaired the installation,
tried to reapply the
security policy (the security.config file was already in the correct
Folder
%AppData%\Microsoft\CLR Security Config\v2.0.50727.42) and tried to
activate the
COM Add-In.

[1] http://forums.microsoft.com/msdn/showpost.aspx?postid=2035333&siteid=1


Does anyone know how to fix this? Many thanks in advance.

Thomas

 

[Ken Slovak - [MVP - Outlook]]

Are there any errors when the addin tries to load? Does it try to load at
all?

Have you checked to see if the addin is disabled? Look in the Trust Center's
Add-Ins tab and look at the disabled items list.

 

[thomas.schager]

Are there any errors when the addin tries to load? Does it try to load at all?
Obviously, the addin does not load; no errors.

Have you checked to see if the addin is disabled? Look in the Trust Center's
Add-Ins tab and look at the disabled items list.

Yes, i checked the Trust Center. My addin is listed as inactive; I
tried to get it active but I had no chance, after opening the Trust
Center again, it is still disabled.

I also tried to uninstall and reinstall the addin, bringing no effect.

Any ideas?


Thanks, Thomas

 

[Ken Slovak - [MVP - Outlook]]

Well, the only thing I can think of offhand if the addin is inactive and not
disabled is to look at the Framework 2.0 configuration utility and make sure
the security is still set as full trust. Other than that I'd suggest posting
in the MSDN VSTO forum, the members of the VSTO team answer questions there
and I'm sure would have other insights to the problem.

 

[thomas.schager]

I just solved my problem, finally!

My addin had no problems with addin security, but other problems on
startup. There was obviously an IOException thrown due to problems
with the configuration XML. The general problem was, that Outlook just
disabled the addin on failures, but does not show any error messages.

As in http://help.lockergnome.com/office/Permissions-problem-VSTO-loading-ftopict1000543.html
described, you need to set the environment variable
VSTO_SUPPRESSDISPLAYALERTS to 0 (in my case I had to create it). To
get error messages helps you somewhat finding errors ;-)

I fixed the startup problem and activated the addin - now it works.



Thomas