We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

InstallNightmares
Posts: 2
Joined: Tue Jun 24, 2014 12:48 pm

VB6 project installer woes

Howdy folks,

(Using AI free edition)

I'm trying to build some reliable installers for some old VB6 apps. we have knocking about.

AI appears to find all dependencies, but when I install the apps. onto a Win 7 machine, some OCX's are not registering.

E.g. COMDLG32.OCX

To get around this, I've added the merge module for the offending OCX's, which seems to have cured the problem(s), but
why didn't AI install & register the OCX's for me?

Should I not rely on AI to find all dependencies?

Thanks

Regards
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: VB6 project installer woes

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

Please take a look on our "How do I register a file?" faq which should be useful for you. Also, please keep in mind that only the "Self register native library" registration option is available within a "Simple" project type. The "Extract registration info from native library" and "Register .NET assembly for COM interoperability" options are available starting with a "Professional" project type.

If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
InstallNightmares
Posts: 2
Joined: Tue Jun 24, 2014 12:48 pm

Re: VB6 project installer woes

Hi Daniel,

Thanks for your reply.

In my AI (simple) projects, no registration is set for all OCX's. Is this the problem? Should I choose Auto register > Self register for all OCX's?

If I had the professional version of AI, how would I know which registration type (auto or extract) to choose from?
Is it trial and error?

In general, what I'm trying to say here is that it is not clear to me how to ensure controls are properly registered. It seems like a bit of a black art to me!

Also, how can I check to see if a control has been properly registered on the destination PC?
(Half the trouble is that I'm not sure what I'm looking for!)

Thanks

Regards,
Darren
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: VB6 project installer woes

Hello Darren,

You're welcome.
In my AI (simple) projects, no registration is set for all OCX's. Is this the problem? Should I choose Auto register > Self register for all OCX's?"
Yes, you should manually enable the "Auto register file (DLL,OCX,etc)" option for all of your files you need to be registered at install time.
If I had the professional version of AI, how would I know which registration type (auto or extract) to choose from?
Is it trial and error?
Please note that it is not recommended to enable the "Self register native library" option as this option has many drawbacks (like not being able to roll back the changes if something fails later in the install) and it is against Microsoft guidelines. The recommended registration options are "Extract registration info from native library" and "Register .NET assembly for COM interoperability".
Also, how can I check to see if a control has been properly registered on the destination PC?
Please take a look on the following threads which could be useful for you:
- How to check if a dll is registered?
- How can I tell whether a DLL has been registered?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”