Ken Slovak

I have some addins for Outlook 2007 developed using Cypress and both VB.NET and C#.

If I run the addins from the VS 2005 IDE they run with no problems. If I compile as release mode they run from the IDE, start Outlook and run with no problems.

However, if I install after compiling the setup project and try to run the addin by just starting Outlook (on the same dev machine) the addins won't run and the error is the ever helpful:

"Not loaded. A runtime error occurred during the loading of the COM Add-in"

In cases like this do I need to follow the deployment steps outlined in

http://msdn.microsoft.com/office/default.aspx pull=/library/en-us/odc_vsto2005_ta/html/officevstowindowsinstallerwalkthrough.asp

Or should the fact that the code is running on the dev machine be sufficient

Thanks,

Ken Slovak

MVP - Outlook



Re: Visual Studio Tools for Office Cypress Outlook 2007 addin installation problems

Patrick Schmid

I figured I'll give it a try here...

I made a new Outlook VSTO add-in, and added a messagebox popup to the startup event.

I installed it via VS on my dev machine, opened Outlook and the add-in wasn't loaded. "The Managed Add-in Loader failed to initialize". I went into VS and launched Outlook in debug mode from there. Add-in worked.

Launched Outlook normally, add-in works now too.

Took the setup project to an XP VM. Same error message, can't get the thing to load.

I figured while I am already annoyed, I can give it a shot in Vista...Same error message.


Patrick




Re: Visual Studio Tools for Office Cypress Outlook 2007 addin installation problems

Ken Slovak

It turns out that you do need to follow the steps in http://msdn.microsoft.com/office/default.aspx pull=/library/en-us/odc_vsto2005_ta/html/officevstowindowsinstallerwalkthrough.asp#officevstowindowsinstallerwalkthrough_creatinginstallerpackagestodeploysolutions to be able to deploy a Cypress Outlook addin, even to the the same machine where the addin was developed. The assembly must also be signed.

I skipped the steps for adding a check for the Outlook 2007 PIA and the VSTO runtime because so far I'm only deploying to other computers that are running Office 2007 and that have Cypress installed. I'm also not sure about the ComponentID for the Cypress runtime and I'm guessing it's not the same as the one for the VSTO 2005 runtime. I also haven't seen any redistributable runtime for Cypress so far, I'm not sure one is available yet.

How would I go about finding the ComponentID of the Cypress runtime so I can add a check for that into the installation prerequisites

Is the ComponentID going to be the same for the release version as it is now

Is there a redistributable version of the Cypress runtime available yet

Thanks,

Ken Slovak





Re: Visual Studio Tools for Office Cypress Outlook 2007 addin installation problems

Martin Sawicki - MSFT

The product code of VSTO 2005 SE runtime is the same as VSTO 2005 so that part of the paper is still applicable to the SE.

There is an additional regkey that enables you to distinguish between VSTO 2005 and VSTO 2005 SE runtime that you can check for:

HKLM\Software\Microsoft\VSTO Runtime setup\v2.0.50727

Update=1

The VSTO runtime deployment paper is in the process of being updated with this and other additional suggestions for VSTO 2005 SE runtime deployment - you should be able to see this hopefully by the end of the year or so.

(Note that the SE runtime deployment story is essentially the same as the VSTO 2005 runtime - we will just be talking about some new suggestions regarding pre-reqs and install checks, since there are so many new MSOffice apps that the runtime can now target)

Hope this helps

Best regards





Re: Visual Studio Tools for Office Cypress Outlook 2007 addin installation problems

Patrick Schmid

The MSDN article is no longer available. What happened to it

Thanks,

Patrick Schmid




Re: Visual Studio Tools for Office Cypress Outlook 2007 addin installation problems

Hiren

Hi,

I am facing a similar situation, guess its encountered pretty frequently.

However, I have checked that the registry key, as mentioned by Martin does exist.

Also, the MSDN article no longer exists.

Does anyone have a concrete solution for this issue

Any help would be appreciated..

Regards,

Hiren