eska
Posts: 8
Joined: Mon Jan 28, 2008 4:42 pm

Register DLL's

Hello,

I'm new with AI..and don't understand WHEN to 'auto register' a DLL.

I have created an MSI.
When installing this MSI on a different PC, I got an error..
After a long search, I detected that a specific DLL must be registered.

How do I know, which DLL's need to have this 'auto register' option set ?
Where / how can I find this ?

With regards,

Eska
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,
How do I know, which DLL's need to have this 'auto register' option set ?
The creator of the DLL knows if the DLL needs to be registered or not. Therefore, if you are not sure about registering a DLL you need to ask the person or company which created it.
Where / how can I find this ?
This option can be found in the "Edit File" dialog in the "Properties" tab (you can see this dialog by double-clicking the DLL in the "Files and Folders" page).
http://www.advancedinstaller.com/user-g ... ialog.html

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
eska
Posts: 8
Joined: Mon Jan 28, 2008 4:42 pm

Hi,

Thanks for you quick answer, but I still have a question.

I have used the AI on a clean machine.
I have selected the 'repacker' option.
Then, I have done the installation of the software from the vendor.
After this, AI 'creates' the MSI.

Doesn't AI know which DLL's / OCX are registered during installation of the software ?

The installed software runs on this machine, so all needed DLL / OCX is registered...

Or am I missing something ?

Eska
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

Please note that the Repackager tool captures only the effects of the installation (the changes made on the system). If the original installation package executes custom code (programs, scripts etc.) or register DLLs then only the effect will be captured (registry entries, files and folders etc.).

It would be impossible for the Repackager to capture the logic of the original installation (like registering a DLL).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
eska
Posts: 8
Joined: Mon Jan 28, 2008 4:42 pm

Hi,

Oke...that's clear for me...

BUT..
Why is the registry-entry HKEY_CLASSES_ROOT\CLSID default 'excluded'?

All registered items should show up in this section, isn't it ?

I know, I propably ask you a 'stupid' question, but that's because it is not quit clear to me...

Hope you can inform me a little bit.

Eska
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,
Why is the registry-entry HKEY_CLASSES_ROOT\CLSID default 'excluded'?
This key is excluded by default because the entries in it are modified very often, therefore the Repackager could get false or useless information.

Note that you can create a custom profile which includes this key (the default profile is not editable).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”