I've created a major upgrade for an application. I've aligned all of my component GUIDS with upgrade sync and resolved all of the issues found. However, many of the files either don't have versions or have been updated and still have the same version listed. When I install my upgrade over my original .MSI it does not replace any of the files that still bear the same version, even though they have different sizes and dates. The best solution I've found is to sequence the RemoveExistingProducts immediatly after the InstallInitialize action to completely uninstall the old app first and then install the upgrade.

How do you handle this situation? Is there a better way to ensure that all of my different files get replaced regardless of version number?
0 Comments   [ + ] Show comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Windows installer won't upgrade any files in a component unless the key file for the component is being upgraded. Windows Installer won't necessarily upgrade a key file if it had been modified by a user or other non-installer process subsequent to being installed the previous time. And windows installer won't necessarily upgrade an un-versioned key file just because its date has changed, unless its file-hash has also changed.

So there are a whole number of different reasons why a file might not get upgraded, and these are reasons by design, generally justifiable.

When I do a major upgrade, I always configure for a complete un-install first.

Answered 01/31/2006 by: williamp
Orange Belt

Please log in to comment