Right now that config file is just being uninstalled and then replaced because of the early sequencing of REP. If REP is "late" then the file update rules mean that the config file won't in fact be overwritten if the user has changed it.
Phil Wilson -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jmcfadyen Sent: Wednesday, July 09, 2008 10:30 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Prevent overwriting a modified text file when upgrading Phil, yeah looks like we are on the same page in understanding. (nice book by the way it has helped me alot) In this case however the OP mentioned he did not want the overwrite effect of REP being early. On another note you could also look at marking the component not to be uninstalled. (this can have both positive and negative side affects) understanding component rules would go a long way here. I believe Rob M wrote a great post on component rules somewhere. Unfortunately I don't have a link handy perhaps Rob can assist with that link reference. Wilson, Phil wrote: > > What's happening when REP is just after InstallValidate ("early in the > install") is that the older product is uninstalled and then the new one is > installed. In this situation Tom's data file just gets removed and then > installed by the new product. > > When REP is "late" in the install the new product is installed on top of > the older version, during which the file overwrite rules are used and > component ref counts are incremented (so your guids should be consistent > for files you care about, and Chris's side effects). Then the "uninstall" > happens, which mainly consists of decrementing the component ref counts. > > So I think we're both saying the same thing, and I don't think my earlier > statement that "A major upgrade will not use file update rules if it's > sequenced early in the install, such as just after InstallInitialize" > contradicts anything you're saying. > > Phil Wilson > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of jmcfadyen > Sent: Wednesday, July 09, 2008 4:53 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Prevent overwriting a modified text file when > upgrading > > > Phil are you sure about this.. (not trying to be difficult I would be > interested to understand what your getting at here.) > > My understanding of the sequencing relating to upgrades is the opposite of > what you suggest. > > by moving the RemoveExistingProducts action earlier in the sequences you > are > effectively removing the older product prior to installing the new one. > > By leaving the RemoveExistingProducts later in the sequences you will have > the opportunity to leave components on the machine during installation of > the newer version. See this post for more details as its quite complex to > explain. This would require that you match component ID on the items you > did > not wish to upgrade. > > http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!249.entry > > > > Christopher Painter-2 wrote: >> >> Read: >> >> http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx >> >> Do be advised that if you aren't following good versioning patterns >> upstream and you move the the action in the sequence, you might see other >> adverse side effects. >> >> >> Christopher Painter, Author of Deployment Engineering Blog >> Have a hot tip, know a secret or read a really good thread that deserves >> attention? E-Mail Me >> >> >> --- On Wed, 7/9/08, Thomas Singer <[EMAIL PROTECTED]> wrote: >> >>> From: Thomas Singer <[EMAIL PROTECTED]> >>> Subject: Re: [WiX-users] Prevent overwriting a modified text file when >>> upgrading >>> To: "General discussion for Windows Installer XML toolset." >>> <wix-users@lists.sourceforge.net> >>> Date: Wednesday, July 9, 2008, 2:04 PM >>> The relevant source code is: >>> <InstallExecuteSequence> >>> <RemoveExistingProducts >>> After="InstallValidate" /> >>> </InstallExecuteSequence> >>> >>> Where should I schedule it instead? >>> >>> -- >>> Tom >>> >>> >>> Wilson, Phil wrote: >>> > Where is your RemoveExistingProducts sequenced? A >>> major upgrade will not use file update rules if it's >>> sequenced early in the install, such as just after >>> InstallInitialize. >>> > >>> > Phil Wilson >>> > >>> > >>> > -----Original Message----- >>> > From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] On Behalf >>> Of Thomas Singer >>> > Sent: Wednesday, July 09, 2008 12:25 AM >>> > To: General discussion for Windows Installer XML >>> toolset. >>> > Subject: Re: [WiX-users] Prevent overwriting a >>> modified text file when upgrading >>> > >>> > I want to add: I've read in the mailing list >>> archive, that the installer by >>> > default should *keep* the file, but for our tests it >>> definitely >>> > overwrites/uninstalls the file. >>> > >>> > -- >>> > Tom >>> > >>> > >>> > Thomas Singer wrote: >>> >> Our installers install also a configuration (text) >>> file where - if necessary >>> >> - the user can configure some options to run our >>> application. Unfortunately, >>> >> it will be overwritten without request when >>> installing an upgrade (different >>> >> Product Id, different Product Version) using >>> "msiexec /i <msi-file>". We are >>> >> using WiX 3.0.4227.0. >>> >> >>> >> How we can prevent overwriting this file? >>> >> >>> >> -- >>> >> Thanks in advance, >>> >> Tom >>> > >>> > >>> > >>> ------------------------------------------------------------------------- >>> > Sponsored by: SourceForge.net Community Choice Awards: >>> VOTE NOW! >>> > Studies have shown that voting for your favorite open >>> source project, >>> > along with a healthy diet, reduces your potential for >>> chronic lameness >>> > and boredom. Vote Now at >>> http://www.sourceforge.net/community/cca08 >>> > _______________________________________________ >>> > WiX-users mailing list >>> > WiX-users@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/wix-users >>> > >>> > >>> > >>> > >>> ------------------------------------------------------------------------- >>> > Sponsored by: SourceForge.net Community Choice Awards: >>> VOTE NOW! >>> > Studies have shown that voting for your favorite open >>> source project, >>> > along with a healthy diet, reduces your potential for >>> chronic lameness >>> > and boredom. Vote Now at >>> http://www.sourceforge.net/community/cca08 >>> > _______________________________________________ >>> > WiX-users mailing list >>> > WiX-users@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/wix-users >>> > >>> >>> ------------------------------------------------------------------------- >>> Sponsored by: SourceForge.net Community Choice Awards: VOTE >>> NOW! >>> Studies have shown that voting for your favorite open >>> source project, >>> along with a healthy diet, reduces your potential for >>> chronic lameness >>> and boredom. Vote Now at >>> http://www.sourceforge.net/community/cca08 >>> _______________________________________________ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> >> ------------------------------------------------------------------------- >> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >> Studies have shown that voting for your favorite open source project, >> along with a healthy diet, reduces your potential for chronic lameness >> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > > -- > View this message in context: > http://www.nabble.com/Prevent-overwriting-a-modified-text-file-when-upgrading-tp18332928p18373287.html > Sent from the wix-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://www.nabble.com/Prevent-overwriting-a-modified-text-file-when-upgrading-tp18332928p18376188.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
