|
Jordan Blaydes
Posts: 37
Joined: 2009-02-08
|
Are there any issues with COM Add-ins when you have two add-in-express add-ins loaded with different versions of add-in-express? Is this even possible?
We have multiple products and we typically keep all product lines upgraded to latest version. Meaning we don't really release our add-ins on different versions.
Our real problem is that we have some customers who run add-ins from other vendors that are using add-in-express and they report conflicts. Typically the add-in the other vendor has doesn't work when ours is enabled and vice versa.
We're not really sure if it's code in our add-in acting up or code in the other vendors add-in causing issues.
They both work when enabled separately. Do you have any guidance on these types of add-in-conflict? Could it be related to mis-matched versions? Is there a guide of FAQ on reducing add-in conflicts when developing Excel Add-ins?
I would appreciate any expertise you have in this matter. We love add-in-express and have used it for years! Sorry for so many open-ended questions. Thanks!
Jordan |
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
Hello Jordan,
Such cases require researching.
Jordan Blaydes writes:
Typically the add-in the other vendor has doesn't work when ours is enabled and vice versa.
What "doesn't work" mean? Is it an exception or crash? Or, the add-ins handle the same event and one of the add-ins cancels it?
Lets start with getting the adxloader.log the add-ins produce when both of them are loaded. You can send the log files to the support email address: see {Add-in Express installation folder}\readme.txt. Also please make sure your email contains a link to this topic.
Andrei Smolin
Add-in Express Team Leader |
|
|
Jordan Blaydes
Posts: 37
Joined: 2009-02-08
|
Thank you for the reply. I know "doesn't work" is not descriptive. I'm looking for general troubleshooting and getting the adxloader.log is the first step. I will post the log here.
Can you confirm any known conflicts with running two add-ins using different versions of Add-in-express on the same machine? Is there anything documented in known issue or in best practices? Is Add-in-express designed to work with multiple add-ins authored using different versions of add-in-express? |
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
Hello Jordan,
Jordan Blaydes writes:
Can you confirm any known conflicts with running two add-ins using different versions of Add-in-express on the same machine?
No.
Jordan Blaydes writes:
Is there anything documented in known issue or in best practices?
No.
Jordan Blaydes writes:
Is Add-in-express designed to work with multiple add-ins authored using different versions of add-in-express?
Yes.
Add-in Express registers your add-in so that the loader is the target DLL that Office loads when it discovers your add-in registered. The loader is a COM add-in itself: it implements IDTExtensibility2 and a number of other COM interfaces. Two loader instances loaded from different locations are different add-ins: they connect to the same events and handle them in the same way. They just cannot intersect. At some stage, the loader creates an AppDomain, loads your assembly into it and then your assembly connect to some Office events. Two assemblies (=two add-ins) *can* intersect: imagine an add-in cancelling an event (such as WorkbookBeforeSave) while getting that event is essential for the other add-in.
Andrei Smolin
Add-in Express Team Leader |
|
Forums
Topics
Search
Help
Login
Register