Patching modified files

Got a problem you cannot solve? Try here.
Post Reply
dawidp
Posts: 31
Joined: Wed Jan 14, 2009 5:45 pm

Patching modified files

Post by dawidp »

Patching files that were modified after the original install on the host machine left the files untouched. That is they were not overwritten by the new version. Is this the default behavior? Can we force the files to be overwritten?

I'm using Web Build btw.

Thanks,
Dawid
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

You should force delete such files which might not be recognized as older versions by Windows Installer.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
dawidp
Posts: 31
Joined: Wed Jan 14, 2009 5:45 pm

Post by dawidp »

Can you tell me how Windows Installer determines which files to patch / replace?

Thanks,
Dawid
dawidp
Posts: 31
Joined: Wed Jan 14, 2009 5:45 pm

Post by dawidp »

Found the answer:

Versioned File
  • 1. If the file version on the target system is the same as that in the setup package, the file is not updated, irrespective of the date.
    2. If the file version on the target system is older than that in the setup, the file is overwritten.
    3. If the file version on the target system is newer than the file within the setup, it is not overwritten.
Non-Versioned File
  • 1. If the file on the target system has a later modified date versus created date, it is not overwritten, as it is considered user data.
    2. If the file on the target system has the same created and modified date, it is overwritten.
    3. If the file on the target system has a created date that is later than the modified date, it is overwritten.
Post Reply