2
votes

I am working on a Outlook 2010 add-in. I have already check this blog. Deploying your VSTO add-ins to All Users (Saurabh Bhatia)

My test environment is the next Win7 64bit with OU2010 32bit. So I registry my add-in into HKLM to allusers install in this way.

Unlike the HKCU registry hive, the HKLM registry hive for Office add-ins is redirected on a 64-bit Windows OS. So if you are trying to register an add-in with 32-bit version of Office running on a 64-bit OS, the add-ins registry will be under the WOW6432Node. The 32-bit Office running on 64-bit OS will always load the add-ins listed under this key.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\application name\Addins\add-in ID

After install I check HKLM, and everything is fine with the registered values(like loadbehavior, and manifest). But in HKCU this registry values doesn't exists. If i put them manually the add-in load without any problem.

What is the problem?

My registry path is the next:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Myaddin

Manifest value: [TARGETDIR]Myaddin.vsto|vstolocal

2
Please share the exact registry path your installer creates and the full value of the Manifest key. If you want to install to All Users - then you don't need HKCU - you need to get HKLM working.SliverNinja - MSFT

2 Answers

2
votes

Your manifest value should be file:///[TARGETDIR]Myaddin.vsto|vstolocal (VSTO Fastpath formatted). The registry path you have is correct for x86 Office on an x64 OS.

0
votes

You should check the names of the registry that you are creating. I had myself stuck for days on the same issue, later to find that I had typo on DWORD "loadbehavior" instead of "LoadBehavior"