Have an installation with the standard mscomctl merge module but it always overwrites the existing mscomctl.ocx. This is causing problems for our developers that need the newer version of mscomctl.ocx. new version:6.1.98.34 old version: 6.1.97.82 I need to explain to the application owners and developers why this is happening. The file versioning rules should be in effect and not overwrite the file.
I assume this is a Windows Installer based project type?
Do you have a logfile? What is the REINSTALLMODE property value? Is this DLL the keyfile of it's own component? Does it have a version override value in the File table?
MSI has been around for nearly 15 years. It behaves in very predictable ways.
This is the standard mscomctl.ocx Windows Common Controls ActiveX Control DLL merge module version 6.1.97.82. The installation is not an upgrade. File Versioning Rules state: Highest Version Wins—All other things being equal, the file with the highest version wins, even if the file on the computer has the highest version.
This is not the case as the newer version is being overwritten with the older version.
You are over simplying the file versioning rules. It's not really relevant that the install is an upgrade.
The rule you cite assumes:
1) That REINSTALLMODE=omus ( I asked what it was, you didn't answer.) 2) That the file in question is the keyfile of a component. 3) That "version lying" hasn't been utilized. (aka "Always Overwrite")
