Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-10 Thread Wilson, Phil
-- 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. (n

Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-10 Thread Rob Mensching
7;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

Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-10 Thread Thomas Singer
homas 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." &

Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-09 Thread jmcfadyen
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

Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-09 Thread Wilson, Phil
tallInitialize" 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

Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-09 Thread jmcfadyen
r 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 >>

Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-09 Thread Christopher Painter
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 >

Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-09 Thread Thomas Singer
tallInitialize. > > 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] Prev

Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-09 Thread Wilson, Phil
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, b

Re: [WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-09 Thread Thomas Singer
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 c

[WiX-users] Prevent overwriting a modified text file when upgrading

2008-07-07 Thread Thomas Singer
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 ". We ar