Hi Amit, The real question you need to answer is - do you think that all of your major upgrades will never change the structure/add new configuration settings in your Config file(s)? Also, component's health/version status is dependent upon a keypath. No matter where you will put RemoveExistingProduct, if keypath is different, component will be reinstalled. Suppose, you will use some static dummy versioned file as a keypath or some registry key. That will solve your problem of not overriding Config files as long as file/registry key is not deleted or corrupted somehow. In this case major upgrade or repair will overwrite user's Config files with files in your original installer. So, if you want truly robust solution you really need to go in the direction of preserving user's values before upgrade/repair and restoring them after upgrade/repair is done.
Sorry for the bad news. Alex -----Original Message----- From: Amit Shrivastav [mailto:[EMAIL PROTECTED] Sent: Sunday, October 19, 2008 1:20 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Major upgrade scenario problem Hi Alexander, There is one more option i think...place RemoveExistingProduct after the tag InstallFinalize. Keep that Config files in the separate component. On the base of keeping RemoveExistingProduct it will not remove all the other files based on the latest versions of the files. And which files are not modified will be keep as it is. Thanks Amit Srivastava On 10/19/08, Alexander Shevchuk <[EMAIL PROTECTED]> wrote: > Amit, > > That is how major upgrade works. If you want to preserve Config files > during major upgrade you have to either copy files to temp folder before > upgrade and restore them after or you need to write custom action which will > read the changes from the Config files, preserve them somewhere (like > registry) and restore these values after upgrade. > > > Alex > > > -----Original Message----- > From: Amit Shrivastav [mailto:[EMAIL PROTECTED] > Sent: Friday, October 17, 2008 2:55 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Major upgrade scenario problem > > HI All, > > Here is the scenario i am working on. > 1) I created a msi. it is deploying some binaries and config files to the > system. > 2) Now we are planning to give major upgrade of that product. In that we are > modifying the binaries but not the config files. > 3) In upgrade scenario if i am mentioning the OnlyDetect="no" then it is > uninstalling the completely previous product including config files as well. > > <Upgrade Id="GUID"> > > <UpgradeVersion Maximum="ver" Property="UPGRADE_PROPERTY" MigrateFeatures=' > yes' IgnoreRemoveFailure='no' IncludeMaximum='no' OnlyDetect='no'/> > > </Upgrade> > > 4) In upgrade scenario if i am mentioning the OnlyDetect="yes" then it is > creating two entries in the add/remove program which we dont want. > > <Upgrade Id="GUID"> > > <UpgradeVersion Maximum="ver" Property="UPGRADE_PROPERTY" MigrateFeatures=' > yes' IgnoreRemoveFailure='no' IncludeMaximum='no' OnlyDetect='yes'/> > > </Upgrade> > > Has anybody faced such type of issue? Please let me know what can i do to > overcome this problem. > > Any help will be appreciated. > > Thanks > > Amit > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
