Hi, I am doing a minor upgrade for an application some dlls are unversioned and some are versioned but it has the same version in the old setup and the upgrade setup. These dlls not replacing after minor upgrade its time stamps are different.
For the case of dll is it will check only version not timestamp?
Log is giving the information "Won't Overwrite; Won't patch; Existing file is of an equal version"
So in the case of file versions are equal for dll it wont check for time stamp? It is a Basic MSI Project.
Any help will be greatly appreciated. Regads, Bineesh
Upgradation of versioned files is starightforward: Higher version component gets installed over lower without exceptions
There are three cases to look at: CASE1: The system has component Abc.dll(or exe) of version 1.0.0.1 installed on it. Your minor upgrade ships Abc.dll of version 1.0.0.2. Abc.dll of version 1.0.0.2 replaces the one already installed on the system.
CASE2: The system has component Abc.dll of version 1.0.0.2 installed on it. Your minor upgrade ships Abc.dll of version 1.0.0.1. Abc.dll of version 1.0.0.2 will not be replaced whatever the timestamp.
CASE3: The system has component Abc.dll of version 1.0.0.1 installed on it. Your minor upgrade ships Abc.dll of version 1.0.0.1. There is nothing to replace.
The fact is, only version numbers matter for versioned files.
You may be able to override the version numbers so that your minor upgrade will work. Right-click on the individual file name in the Files View, click properties, and enter a higher version number.
The MSI will build with the higher number so that the comparison will be "tricked" into thinking it has a higher version and should replace it.
This isn't the "best practice" (you should change the version number for newer versioned files), but it may help you get around your issue.
