I am getting a failure when registering a dll using the Auto Register > Extract Registration info > Synchronisation Enabled option. The dll is registered on my local machine in a dev location, and is being referenced by a Word macro enabled template through the VBA references dialog.
I create an msi using advanced installer 8.8.1 and am installing both the dll and word template to different locations. If I use the extraction option then word fails to see the dll at it’s new location, but if I use Self Registration (which is not recommended) then my word template picks up the dll in the different location from where it was developed in.
This isn’t all though.
If I use the Extraction method, so my Word addin does not find the dll, I can then use the VBA references dialog to locate and attach the dll to my Normal template, and all of a sudden my addin finds it too. Both addins (the normal and my own) can use the dll without any COM failures, which would indicate the dll is correctly registered.
However, if I then remove my reference in the Normal template, uninstall my package and search the registry for my dll, I find 5 entries that have not been removed. This leads me to think that these entries were put there, not by the Advanced Installer msi package, but when I referenced my dll in the normal template. These entries appear crucial to Word locating my dll correctly.
Can you shed any light on this issue. I can supply my dll and addin (they are very simple hello world tests), the AI package and msi, the run log, and the registry settings that remain afterwards.
Im using windows 7 64bit & Office 2010 32bit for both the development and test environment.
Thank you.
FOLLOW US
Get the latest news in Application Packaging