GS
2019-12-02 16:11:24 UTC
Hello,
I've been using my VB6 AddMan4XL.exe for some years now to manage
(load/unload/install/remove) VBA addins with the various installed versions I
use for testing. This app lists by ver each addin stored in each version HKCU
Registry key under...
Software\Microsoft\Office\n.0\Excel\Add-in Manager
and
Software\Microsoft\Office\n.0\Excel\Options
..where they are listed by version, and the former key lists installed while
the latter lists loaded. There's some shifting back and forth to load/unload
but for all intents and purposes if an addin isn't listed here then it's not
installed (registered) with Excel.
I'm trying to extend my app to include COMAddins management in the same fashion
but the logistics aren't as simple as they might seem. For instance, depending
on the scope (current user or all users) of a COMAddin when it's being
installed, it will be registered under HKCU or HKLM respectively. The path for
either is under...
Software\Microsoft\Office\Excel\Addins
..where just the COMAddin info is listed without respect to Excel version[s].
Unfortunately, each version COMAddin Manager dialog does not agree with the
registry lists nor with each of the other version lists! Also, each version
COMAddins Manager dialog uses a checked list to determine if the addin is
loaded or not at runtime.
What I need help with is finding where this info gets stored between runtime by
each Excel version so I can make my app work with COMAddins same as it does
with VBA Addins. Can anyone shed any light on this or point me where to find
good info?
TIA
I've been using my VB6 AddMan4XL.exe for some years now to manage
(load/unload/install/remove) VBA addins with the various installed versions I
use for testing. This app lists by ver each addin stored in each version HKCU
Registry key under...
Software\Microsoft\Office\n.0\Excel\Add-in Manager
and
Software\Microsoft\Office\n.0\Excel\Options
..where they are listed by version, and the former key lists installed while
the latter lists loaded. There's some shifting back and forth to load/unload
but for all intents and purposes if an addin isn't listed here then it's not
installed (registered) with Excel.
I'm trying to extend my app to include COMAddins management in the same fashion
but the logistics aren't as simple as they might seem. For instance, depending
on the scope (current user or all users) of a COMAddin when it's being
installed, it will be registered under HKCU or HKLM respectively. The path for
either is under...
Software\Microsoft\Office\Excel\Addins
..where just the COMAddin info is listed without respect to Excel version[s].
Unfortunately, each version COMAddin Manager dialog does not agree with the
registry lists nor with each of the other version lists! Also, each version
COMAddins Manager dialog uses a checked list to determine if the addin is
loaded or not at runtime.
What I need help with is finding where this info gets stored between runtime by
each Excel version so I can make my app work with COMAddins same as it does
with VBA Addins. Can anyone shed any light on this or point me where to find
good info?
TIA
--
Garry
Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion
Garry
Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion