Unclear on registering DLLs and OCX components - Advanced Installer Community

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!

Kris
Posts: 3
Joined: Fri May 01, 2009 9:05 pm

Unclear on registering DLLs and OCX components

I have a bit of a conceptual problem with AI... It is not as intuitive as I'd hopped it would be. And help is not written very well. Because of that I need some clariffications... many of them

So,,, I have a package that I need to deploy several dll files and ocx files with. That is all fine,,, I package them no problem... however,, those files need to be registered with the OS.

Here is a whole range of issues.....

If I set the components to auto register,,, then on VIsta and XP,,, the components registrations fail, which prevents the instillation to go through. This is a good thing and it is supposed to happen because Vista and XP will automatically prevent the components that exist and are registered to be overwritten. So the issue is NOT in my dll's or OS... the issue is in the installer that is attempting to register components which exist and are already registered.

Then,, If I set the components to NOT auto-register,,, WHAT DOES THAT MEAN? Will the register if they don't exist or will they simply NOT REGISTER?
I can't find a single reference in help files that explains this.

Then,,, If I set the components to "Never Overwrite",,, things seem to start making sense,, but then I am not sure how to combine all this?

Should I set the components to auto-register OR Not?
Will they register automatically if they don't exist?
If I set them to auto-register and to "never overwrite" does that mean that Vista installation will work fine?

ALSO

When I set the installer to "Run only if user has administrator privileges" what exactly does this mean.... Is the msi package set to work as INVOKER or forces admin?

I mean,,, your software seems to do a lot of cool stuff but your help sucks. I have wasted 3 days on this.

I would really appreciate a concise and clear explanation on these issues.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Unclear on registering DLLs and OCX components

Hi,
If I set the components to auto register,,, then on VIsta and XP,,, the components registrations fail, which prevents the instillation to go through.
I'm not sure why the registration process fails. Can you please give me more details about the exact behavior you are encountering? Also, can you please send us the .AIP (project) file and a verbose log of the install process to support at advancedinstaller dot com so we can investigate them?
This is a good thing and it is supposed to happen because Vista and XP will automatically prevent the components that exist and are registered to be overwritten.
Under normal circumstances, registering a DLL which is already registered should overwrite the existing information.
Then,, If I set the components to NOT auto-register,,, WHAT DOES THAT MEAN? Will the register if they don't exist or will they simply NOT REGISTER?
If the Auto register file (DLL, OCX, etc.) option is not enabled, the file is not registered.
Then,,, If I set the components to "Never Overwrite",,, things seem to start making sense,, but then I am not sure how to combine all this?
Please note that the "Never Overwrite" component attribute makes sure that future packages which will be installed on the target machine will not overwrite the component. This does not refer to overwriting existing files when the install process runs.
Should I set the components to auto-register OR Not?
Yes, if the files need to be registered.
Will they register automatically if they don't exist?
Only if they use the auto-register option.
If I set them to auto-register and to "never overwrite" does that mean that Vista installation will work fine?
No, I think the problem is caused by something else.
When I set the installer to "Run only if user has administrator privileges" what exactly does this mean.... Is the msi package set to work as INVOKER or forces admin?
This predefined launch condition makes sure that the package doesn't run if the user doesn't have Administrator privileges. If this option is set and a limited user runs the package, the install will stop. If you want to always run the package with Administrator privileges, you can use the execution level for the bootstrapper.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Kris
Posts: 3
Joined: Fri May 01, 2009 9:05 pm

Re: Unclear on registering DLLs and OCX components

I also have icons breaking down when I assign the icon file to the icon. Even the uninstall icon is broken.

I can create an aip file and an install package that contains everything that I need it to contain and send it. If you can test that against Vista and XP that would be great.

I went back to AI 6.5 and it seems like I don't have some of the problems (icon related ones). I still have registration problems.

There is also an issue with providing MDAC. If the user comp has MDAC components installed and registered the Merge module should not attempt to overwrite with an older version of MDAC.
As for the normal circumstances and overwriting files.

When installer uses system or mdac files and the OS has those files installed an registered, AND the files in the OS are newer then the ones supplied then overwriting should NOT happen. There should be an option to not overwrite (as per install) and an option to skip registering if file exists and is registered.

This is the reason I am saying this...

Vista comes supplied with DAC 6.0,, yet most developers still use MDAC which ranges from 2.3 to 2.8. MDAC files are not supposed to be touched, uninstaller or re-installed. You can break the entire Data Access structure of the OS...

Now,, when I supply an install package with MDAC 2.7 merge module this mostly flies for non vista OS,,, Vista however won't hear about that MDAC version which halts the install. Makes it very unattractive to the buyer of the software.

It may be me,, but i couldn't find a option for merge modules to set them to install only if they don't exist. Well I am talking specifficaly about MDAC components.

there is so many details about this,, I could write you a book.

BTW, I apologize for the angry outburst at the end of the previous post. I was just very frustrated.

Let me know if you can take on the install package to test along side aip
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Unclear on registering DLLs and OCX components

Hi,
I also have icons breaking down when I assign the icon file to the icon. Even the uninstall icon is broken.
Can you please give me more details about this? What is the exact behavior you are encountering?
When installer uses system or mdac files and the OS has those files installed an registered, AND the files in the OS are newer then the ones supplied then overwriting should NOT happen.
By default Windows Installer does not overwrite files which are newer than the one in the package. Does your package show a different behavior?
There should be an option to not overwrite (as per install) and an option to skip registering if file exists and is registered.
I'm afraid Windows Installer doesn't offer this functionality directly. However, you can try using a search to determine if a file is registered or not. The property of the search can then be used to condition the component of the file in the Organization page.
Now,, when I supply an install package with MDAC 2.7 merge module this mostly flies for non vista OS,,, Vista however won't hear about that MDAC version which halts the install. Makes it very unattractive to the buyer of the software.
It may be me,, but i couldn't find a option for merge modules to set them to install only if they don't exist. Well I am talking specifficaly about MDAC components.
When adding a merge module to a project you can specify which feature will contain it. In your case, you can have a feature which will be installed only on Windows versions older than Vista and add the merge module in it. For this feature you can set a conditional install level which uses the VersionNT property.
Let me know if you can take on the install package to test along side aip
Sure. After modifying the project you can send it to us for investigations if the package doesn't work correctly. In your email please mention the exact problems you are encountering.

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

Return to “Common Problems”