I’m not sure whether I fully understand your question. It seems to me that parts are missing, as you talk about custom actions, which I cannot see.

The method I describe – at least the first part – leaves the registration of the add-in up to the installer logic. There’s no need for any custom actions. My problem was that uninstalling my add-in left the office toolbar it created – now completely useless – in PowerPoint. I solved that by making the toolbar temporary by setting the Temporary property to True. (This only applies to Office 2003 and less. If you’re only targeting Office 2007 and above, then you don’t have to worry about temporary toolbars and you can leave the installation and uninstallation up to the installer logic.)

The second part describes how you can use a custom action to manually call the DllRegisterServer function to install, and the DllUnregisterServer to uninstall your add-in. You would only need this if you are targeting Office 2003 and less, and cannot make your toolbar temporary.

You mention the adxloader.dll and a manifest, so I assume you have a .NET add-in. I must admit that I’m not too familiar with .NET. The method I described (second part) works for VCL add-ins.

Best regards,
Fokke Post

I’m using wix and what i did is to add the adxloader.dll and manifest as part of the files in the installation-directory and add the following custom actions:

And the following action runs (under ):
(NOT UPGRADINGPRODUCTCODE) AND (REMOVE=”ALL”)

NOT Installed

It seems to work fine in all the test we ran so far (the wix-installer version still isn’t in production).
Can you please elaborate how the method above is better than what i’m using?

Thanks,
Lev Waisberg
Senior Developer – Offisync