Add-in NOT loaded at startup with the new Addin-express version

Add-in Express™ Support Service
That's what is more important than anything else

Add-in NOT loaded at startup with the new Addin-express version
 
Oscar Maire-Richard




Posts: 3
Joined: 2012-07-20
Hello,

We've installed the new Addin-express version for our addin to work in Office 2016 and we've found some issues with the new compilation. An .msi and setup.exe files are created after it (among the .dll corresponding to our addin) as always. For the first time installation process there is no problem, the setup executes the msi and the addin is correctly registered and loaded at startup in any Office program.

But for the update process is different. We don't want our clients to uninstall and re-install the whole program (and thus the addin). Notice that we have many addins not only this one for Office. So, the steps followed in this process are:

1. Our client program checks whether there is a new update.

2. If so, it execute an vbs that:
- Downloads the files that have changed and overwrite those inside the addin's folder. In this case, these files are: AddinExpress.MSO.2005.dll, adxloader.dll, adxloader64.dll, adxregistrator.exe and our addin dlls.
- It finally executes the command: adxregistrator.exe /install="our_addin.dll" /privileges=admin /CLRVersion=2.0

After that, the addin is not loaded at startup when opening any Office program (for any version). Even changing manually the registry key HKEY_CURRENT_USER\Software\Microsoft\Office\Word\AddIns\Our_Addin\LoadBehavior many times it doesn't work. We have noticed that there have been created registry entries in both HKCU and HKLM for the addin that are possibly blocking each other. Uninstall (adxregistrator.exe /uninstall="our_addin.dll" /privileges=admin) and re-install (adxregistrator.exe /install="our_addin.dll" /privileges=admin) the addin does not work (even manually deleting this keys). And the adxregistrator.log shows that everything goes well, exiting with "Success, The add-in registration process is completed with HRESULT = 0...".

One of the solutions for our addin to be loaded at startup is open Word, Excel,... as Administrator, delete the addin from COM add-in and reload it (selecting adxloader.dll in the app folder). But doing this for every Office program is quite tedious for several computers.

We've found a similar issue in https://www.add-in-express.com/forum/read.php?PAGEN_1=2&FID=5&TID=12256 but we already have the RegisterForAllUsers = true in our project, have unregistered and registered it again.

Are we doing something wrong that leads us to have this behavior?

Thanks in advance.
Posted 05 Nov, 2015 08:28:07 Top
Andrei Smolin


Add-in Express team


Posts: 18793
Joined: 2006-05-11
Hello Oscar,

Oscar Maire-Richard writes:
If so, it execute an vbs


Are you saying you register a per-machine add-in from VB Script? Do you get elevated privileges required to register such an add-in?

Also note that Outlook must be closed when you unregister the previous add-in version otherwise I may be unable to overwrite add-in files.


Andrei Smolin
Add-in Express Team Leader
Posted 06 Nov, 2015 06:28:59 Top