gjvdkamp
Posts: 39
Joined: 2018-08-28
|
|
Andrei Smolin
Add-in Express team
Posts: 17493
Joined: 2006-05-11
|
Hello,
The entry you've found is used by a 64-bit Excel to load your add-in using adxloader64.dll. A 32bit Excel uses adxloader.dll to load your add-in.
I ask you to search that guid in your registry and note all the entries in HKCU. I assume your add-in is per user; if this is the case, this guid mentioned in HKLM would be an indication of something is wrong.
Also, make sure you have the add-in ProgId mentioned in HKCU. Say, I have the add-in ProgId="MyAddin139.AddinModule". Accordingly, I have these keys with that ProgId:
- HKEY_CURRENT_USER\Software\Classes\CLSID\{guid} - this is the one you've found; InprocServer32 points to adxloader64.dll
- HKEY_CURRENT_USER\Software\Classes\MyAddin139.AddinModule - this is the ProgId key mentioned in the manual
- HKEY_CURRENT_USER\Software\Classes\WOW6432Node\CLSID\{guid} - this is used by a 32bit Office: InprocServer32 points to adxloader.dll
HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\AddIns\MyAddin139.AddinModule - this is the add-in key
Make sure you unregister the add-in project from the VS IDE and then install the add-in using ClickOnce or you can simply double-click the .application file.
Regards from Belarus (GMT+3),
Andrei Smolin
Add-in Express Team Leader |
|
gjvdkamp
Posts: 39
Joined: 2018-08-28
|
I've found these on my computer, can't access the affected computer today. Will probably need to continu this after the weekend. |
|
Andrei Smolin
Add-in Express team
Posts: 17493
Joined: 2006-05-11
|
No problem.
Regards from Belarus (GMT+3),
Andrei Smolin
Add-in Express Team Leader |
|