Installing VSTO Office Visio 2010 Addin For All Users using Installshield

[heathlmorris]

This is an obscure subject that is difficult to resolve using the references currently on the internet.

After the Developement team has created the VSTO Addin inside Visual Studio 2010 and you have all the binaries and manifest files with embedded digital signatures inside the manifest and vsto file. e.g.

addin.dll
addin.manifest
addin.vsto

You need to install the digital certificate inside the trusted publishers store on the machine using either a commit or deffered custom action. I use certmgr.exe with this commandline to do so

CertMgr.exe -add -c Certificate.cer -s -r localmachine trustedpublisher

Now that you have a trusted publisher certificate on the machine the addin with the same certificate is now trusted. 🙂

All that is left to do is put the correct registry entries inside the registry for the addin.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Visio\Addins\NameOfAddin]
"Manifest"="[INSTALLDIR]addin.vsto|vstolocal"
"Description"="addin"
"FriendlyName"="addin"
"LoadBehavior"=dword:00000003

Manifest is the vsto file and the pipe followed by vstolocal ensures that your addin finds the local resource and does not go on th web to install it

description and friendly name is what your addin will show up as inside the menus and toolbars of the Office Application

LoadBehavior 3 means load at startup.

This example is for Visio, but For Other Office Products it is similar

Heath Morris

[Barbara]

Thank you for this very helpful thread. It saved me a lot of time.

Barbara

[denis1234]

"Could not find default endpoint element that references contract 'IService' in the ServiceModel client configuration section."

So, why this happens and executing InstallShield app with vstolocal manifest?