I assume you are referring to RemoveExistingProducts, not RemoveExistingFiles (I've never heard of that action).
Scheduling RemoveExistingProducts before the installation causes the previous installation being replaced to be first removed, removing references to your (old) components causing them to be erased from the file system/registry/etc. before your newer versions of those references are written. Thus, NeverOverwrite doesn't apply. In your Upgrade table you have a row where you identify a property with the product(s) that you will remove. For purposes of illustration I will assume that property is named OLDPRODUCT (it will be named whatever rows you didn't tag with OnlyDetect="yes"). You would then add " AND NOT OLDPRODUCT" to your "NOT Installed" condition (so it will look like "NOT Installed AND NOT OLDPRODUCT") for launching your readme pdf file. Be sure to replace OLDPRODUCT with your actual property's name to use my fix. -----Original Message----- From: Giora keinan [mailto:grkei...@gmail.com] Sent: Monday, January 18, 2010 1:15 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Minor Upgrade and original msi file name. Thanks Blair Just to be sure that I understood. If my major upgrade removes the existing files. I should use the major upgrade product id in the next minor upgrade. In my major upgrade I see a behavior I don't understand. If the RemoveExistingFiles is schedule before the installation, part of the registry keys are removed (they have a NeverOverwite=yes in the upgrade). If the RemoveExistingFiles is schedule after InstallFinaize the registry keys are left with there values before the installation, but I have a problem that a readme.pdf file that I am launching in the original installation is launched at the end of the upgrade. There is no launch command in the upgrade. Can I prevent the launch of this file ? Thanks Giora . Blair wrote: > 1. Minor upgrades, by definition, use the ProductCode (produ...@id) of the > already installed package. Major upgrades, by definition, use a different > ProductCode. Definitionally, there is no other difference. The rest is > supporting each of the two different upgrade mechanisms. > > 2. The easiest way is: > > <?ifndef var.ProductCode?> > <?define ProductCode="*"?> > <?endif?> > > <Product Id="$(var.ProductCode)" ...> > > -----Original Message----- > From: Giora keinan [mailto:grkei...@gmail.com] > Sent: Monday, January 18, 2010 6:15 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Minor Upgrade and original msi file name. > > Hello > Thanks for the quick answer. > > I have two quick questions: > 1. My understanding is that if I want to do minor upgrade after a major > upgrade I should use the Major upgrade product id instead of the > original installation product id. > 2. Is there a way to do an ifdef in the wxs file. I want to use the same > wxs file for both minor and major upgrades with an ifdef inside. > > Thanks > Giora > > > > Bob Arnson wrote: > >> On 1/17/2010 11:10 AM, Giora keinan wrote: >> >> >>> I have a problem in minor update. In minor upgrade the msiexec is >>> looking for the upgrade name, which should be the same as the original >>> msi name. >>> The problem is that sometimes the original setup filename is modified >>> during download. For example setup.msi is modified to setup(1).msi. >>> >>> >>> >> Use major upgrades and/or an .exe bootstrapper to install minor >> upgrades. http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/ >> >> >> > > -- ------------------------------------------------- Giora Keinan CapsCake - The natural language launcher. Because free text is easy. http://www.capscake.com ------------------------------------------------- ---------------------------------------------------------------------------- -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
