VSTO COM Add-In ProgID

I am having a problem when I ProgID

add-in MyAddin whereas I want it to be MyAddin.Connect because there are many existing tables where VBA refers to MyAddin.Connect .

I changed each instance of MyAddin to MyAddin.Connect in the csproj , manifest and vsto file . I have changed every instance in the registry.

Even the registry key HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Office \ Excel \ Addins \ MyAddIn
in MyAddIn.Connect

However, when I check ProgID

for VBA, it says MyAddin (the friendly name in COM Add-In Manager is MyAddin.Connect).

Where exactly is loaded ProgID

from VBA to Excel? I should note that it worked great when I debugged AddIn through Visual Studio. But when I install it via InstallShield install it just refuses to work.

+3


source to share


1 answer


When we debug AddIn through Visual Studio, an entry for AddIn is added to the registry and from there it loads this addin.

When installing AddIn from InstallShield, we need to check if we have added the registry entry for AddIn correctly or not.



Also check the same registry key under HKCU

. As the addin is loaded from the HKCU branch as well as from the registry.

+1


source







All Articles