If I make a change to the manifest file to point to this QA addin, then the first one does not get loaded correctly. however it has always loaded correctly as well until the most recent version. We have a second QA addin (.AddIn.dll) that is deployed to the same folder and does not exist in the manifest file. That is the addin that is being loaded correctly. The manifest file does describe the addin that is listed above (.dll) in the adxloader log I sent. Startup directory: C:\Users\jputman\AppData\Local\Apps\MyApp\MyAppOffice\ Is there some change in this latest version that could have caused this?Īdd-in Express Loader Log File: 11:03:53:500 It appears there is something in the adxloader / adxloader64 that has changed and is causing the failure, because if I replace these files with the previous version and leave the other upgraded components, it does load correctly.
A runtime error occurred during the loading of the COM Add-in" In the Options > Addins dialog, if you view the COM Addins dialog and click on this addin, it shows "Not loaded.
Once I updated the components to the release, one of the addins stopped loading. The two Addins are deployed to the same directory on the user's machine and are loaded by adxloader64.dll. I work on a product that has two addins installed to a user's machine and are both loaded into Excel at startup.
0 kommentar(er)
