Hi,
I'm using Advanced Installer 9.6.1 but have verified that this problem exists in the current evaluation download of 10.8.
In my installer I am registering an ActiveX DLL file by using the following properties in the 'Registration' properties tab:
[*]Auto register file (DLL, OCX, etc): ticked
[*]Extract registration information from native library: selected
[*]Synchronization: Buildtime
However, when I attempt to use the DLL after running my installer I get a 'Library not registered' error.
If I use regsvr32.exe to register the DLL it works correctly.
I have compared the registry entries written by my installer with those written by regsvr32 and it looks like my installer is failing to write some 'Typelib' entries. On the surface this seems similar to an old post here: http://www.advancedinstaller.com/forums ... =2&t=11233, but it's not clear what the resolution was in that case.
I realiase that two solutions to this problem might be:
1) to use self-registration
or
2) add the necessary typelib definitions using the COM tab
but the Advanced Installer documentation suggests that self-registration is not best-practice and the DLL in question (from a 3rd party) does not come with a type library file.
Is there any way I can get my installer to behave in a similar way to regsvr32 without having to use self-registration or manually adding a type library?
FOLLOW US
Get the latest news in Application Packaging