This project has moved and is read-only. For the latest updates, please go here.

Registry Entries for Addin Deployment

Sep 19, 2013 at 2:43 PM
Edited Sep 19, 2013 at 2:44 PM

NetOffice is simply GREAT.

I have developed Office Addin using NetOffice and its working perfectly with Office 2007, Office 2010 and Office 2013.

Now i want to deploy the Addin using an Installer. I have good experience with NSIS and i have already deployed VSTO Addins using NSIS.

As per my understanding to deploy my addin i have to create registry entries among other things.

So, could anyone please guide me about what should be the registry entries?

Sep 23, 2013 at 4:19 PM
Edited Sep 23, 2013 at 4:43 PM
It's a question I will want answering soon. I know the VSTO ones are like this:

Windows Registry Editor Version 5.00

"Description"="Mail Alert Utils"
"FriendlyName"="Mail Alert"

However my Eset Nod32 addin is like this:

Windows Registry Editor Version 5.00

"FriendlyName"="ESET Outlook Add-in"

But I don't know about netoffice com addins and where does Outlook get the path of the addin from?

Just found this
Sep 29, 2013 at 11:01 PM
first you dont need the manifest key in netoffice. (all other things looks good)
about the addin path:
have a look:

"ESET.OutlookAddin" is the registered ProgID from your Addin, The ProgID is stored in the HKEY_CLASSES_ROOT registry hive with the corresponding codebase.
this is why you need a registration(typical regasm or installer) in the deployment system, and the static register/unregister methods in your addin.

You have to set the ProgID with the Progid Attribute for you addin class.