My Outlook VSTO 3.0 does not load

Question

I am trying to diagnose why my Outlook plugin written in C # / VSTO 3.0 / VS 2008 does not load after installation.

The plugin works fine on my development machine on which Visual Studio 2008 is installed. I cannot expect all my users to have all the prerequisites, so I went through these steps to write the installer: http://msdn.microsoft.com /en-us/library/cc563937(loband).aspx

I installed the add-in on a new Windows XP machine with Service Pack 2 (SP2) with a fresh installation of Outlook 2007. It installs all the prerequisites (.NET 3.5, VSTO 3.0, Windows Installer 3.1, 2007 PIA). Vista starts, but the add-in does not start. If I go to the add-ons tab in the Trust Center, I see the add-in in the "Inactive Application Add-ons" section with the message "Not loaded." An error occurred while loading the COM add-in. "

I don’t know how to find a specific error so that I can fix it.

The reg keys look fine. In HKEY_CURRENT_USER \ Software \ Microsoft \ Office \ Outlook \ Addins \ BlahAddin I see a description, FriendlyName, LoadBehavior (set to 3 until it works, after which, if it is set to 2) and the manifest.

I tried the trick of the environment variable VSTO_SUPPRESSDISPLAYALERTS, and then started Outlook from the command line, but the output did not exit.

My remote debugging more or less works, but I'm not sure what to look for. I do not see my DLL loading when I connect to Outlook, but then again, maybe the managed DLLs do not display the same in VS.

Any other ideas on the next steps that I could follow to create a specific error that I can diagnose?

Answer 1

. "Manifest" . Visual Studio, ​​ Visual Studio 2008 SP 1, , , . , , . , ?

Answer 2

, try-catch , Outlook, , - . , Startup , .

Answer 3

, , . MSVCMON.EXE ( Visual Studio ) ( UNC-) Outlook (.NET) .

, XP Virtual PC 2007 ( ) HD , , , /, .

Are you installing a Debug build or releases? Perhaps one taste has different requirements. Just guessing.

-Mike [MSFT Office Dev]

Answer 4

On your computer, when you run addin from Visual Studio, it should create a registry key in HKEY_CURRENT_USER \ Software \ Microsoft \ VSTO \ Security \ Inclusion {SomeGuid}. Make sure that these registry settings are also deployed with your addition. These are the ones that let you trust your code.