Does IW check for file versions before writting a DLL or OCX

wxperson99 · Postby **wxperson99** » Mon Sep 28, 2015 4:38 pm

I install a number of DLL and OCX files with my install.

I migrated from Wise which had an option to NOT overwrite files that had a newer version on the target PC.

I do not see that in IW. The only copy options I see are Shared DLL, Permanent File (do not uninstall) and Never Overwrite.

Simple question... How can I keep from installing an older version of a DLL or OCX onto a target PC? i.e. leave the newer version on the PC. I do however want to overwrite older versions of the DLL or OCX.

Thanks,

George

wxperson99 · Postby **wxperson99** » Tue Sep 29, 2015 10:11 am

Anyone know the answer to this?

Postby **FrancescoT** » Tue Sep 29, 2015 11:33 am

Dear Wxperson99,

the "Overwrite" option depends on which engine is based your setup (Windows Installer Engine or IA Native Engine).

Generally a new created project is by default based on Widow Installer Engine. Unless the Native setup template has been used to generate the project or the Native Engine has been explicitly activated from the script.

The Windows Installer engine behavior is to overwrite files on the target system only if the ones you are copying are newer or have an higher version.
This behavior cannot be changed with the Windows Installer engine.

Similarly, the Native Engine by default will not overwrite files on the target system if the ones you are copying are not newer, however overwrites may be forced by setting the pre-defined variable NATIVE_OVERWRITE_OLDER to TRUE. However, this is not recommended as it may compromise target system integrity and may break other applications.

Hope this helps you.

Regards

wxperson99 · Postby **wxperson99** » Tue Sep 29, 2015 11:50 am

The Windows Installer engine behavior is to overwrite files on the target system only if the ones you are copying are newer or have an higher version.
This behavior cannot be changed with the Windows Installer engine.

OK.. So unless I did something to force a "Native Setup"... which I am not aware of doing since I am new at this. :-)

.... I should be OK.

Thanks,

George

wxperson99 · Postby **wxperson99** » Fri Oct 16, 2015 9:27 am

ONE MORE THING..

How is "newer" defined. Version number or the date/time stamp of the DLL or OCX, etc..

Thanks,

George

Postby **FrancescoT** » Fri Oct 16, 2015 11:16 am

Dear George,

I am not quite sure to follow your question ... the date/time stamp is always present with any kind of file or folder.

Regards

wxperson99 · Postby **wxperson99** » Fri Oct 16, 2015 11:27 am

Yes... every file has a date/time stamp but...

Every DLL or OCX also has a version number associated with it. i.e. just like the version number of Installaware, etc.. See attached image as an example.

When Installaware makes sure that only newer DLL or OCX files are installed... how does the software determine that... by looking only at the date/time stamp of the file OR by comparing file versions.

The reason I ask is that the only 100% reliable way is to compare the file versions since date/time stamps can sometimes change.

Thanks... George

Postby **FrancescoT** » Fri Oct 16, 2015 12:38 pm

Dear George,

it's the version (if present) that takes the precedence during the comparison process. The date stamp is used when the file doesn't include a valid version number.

Hope this helps you.

Regards