J
John B
Is there any way to prevent the loading of addins using vba or automation?
Because a user may have many addins, potentially hundreds, installed, most if
not all having nothing to do with a current project. I am specifically
interested in Visio but the problem is general to Office. Is there some way
to get at application.COMAddins ( that is what it is called in visio) to set
Connect = false for all addins before the dlls are loaded? "All user" addins
do not even appear in the menu list so the user can deselect them and in the
case of visio drawing controls used in a container app, there is no menu item
at all unless it is added to the UI by the developer.
It is really hard to understand why microsoft thought it was good idea to
load all addins all the time unless the user somehow prevents them from being
loaded instead of only loading the addins the user explicitly selects. If
developers start using drawing controls and since drawing controls do not
support vba, this will become a bigger and bigger problem if each of them
uses addins to support the control. In that case, each container app will
have one or more addins that is specific to that application and eventually
there could be hundreds of these being loaded everytime someone launches any
visio related app.
Because a user may have many addins, potentially hundreds, installed, most if
not all having nothing to do with a current project. I am specifically
interested in Visio but the problem is general to Office. Is there some way
to get at application.COMAddins ( that is what it is called in visio) to set
Connect = false for all addins before the dlls are loaded? "All user" addins
do not even appear in the menu list so the user can deselect them and in the
case of visio drawing controls used in a container app, there is no menu item
at all unless it is added to the UI by the developer.
It is really hard to understand why microsoft thought it was good idea to
load all addins all the time unless the user somehow prevents them from being
loaded instead of only loading the addins the user explicitly selects. If
developers start using drawing controls and since drawing controls do not
support vba, this will become a bigger and bigger problem if each of them
uses addins to support the control. In that case, each container app will
have one or more addins that is specific to that application and eventually
there could be hundreds of these being loaded everytime someone launches any
visio related app.