Luke
Posts: 22
Joined: Thu Oct 11, 2012 11:00 am

DLL registration missing registry entries

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?
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: DLL registration missing registry entries

Hello Luc,

I'm not sure why you encountered this behavior. Here is an alternative solution given by a colleague on the forums:
Auto register DLL not working.

Please let us know if that helped.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Luke
Posts: 22
Joined: Thu Oct 11, 2012 11:00 am

Re: DLL registration missing registry entries

I've had a look at that other thread but the suggested solution seems to be to use Regsvr32.exe via a custom action. I think this will have the same effect as simply using the 'Self register native library' option in the 'Registration' properties tab, which I know works but I was trying to avoid it as the documentation states 'The self registration method of registering components has many drawbacks'.

Anyway, if there is no other solution then I will have to go with self-registration. Thanks for your help.

Return to “Common Problems”