Hi Lincoln, I went a little further in my investigations. You were right for the arguments used during the minor upgrade....
I'm using the Wix bootstrapper (setupbld) to deal with these installation/upgrade issues. And the bootstrapper sets the REINSTALL=ALL REINSTALLMODE="vomus" flags for a minor upgrade. The problem is that, according to the MSDN, REINSTALL=ALL only reinstalls the previously installed features. So I am not able to add new features on a minor upgrade. However, contrary to what I thought, I *am* able to add new components to an existing (installed) feature. The reason why my upgrade failed was that another component had also been removed. I wasn't aware of this removal and, removing a component on a minor upgrade *is* clearly forbidden. I've set the MSIENFORCEUPGRADECOMPONENTRULES property on, so that this kind of surprise won't happen again.... So I'll have to go through a major upgrade this time, but minor upgrades will do the trick next time. Thanks to all of you for following my problem. Fred Lincoln Y Lavoie a écrit : > Hi Fredrick, > > I'm going to guess it may have something to do with the arguments for > the msiexec on the minor update. The arguments specify things like, > replace files only if..., etc. I would make sure there isn't one that > specifies to add files/features not previously present. > > Cheers, > Lincoln > > Frédéric Viollet wrote: >> Hi Rob, >> Thanks for your answer. >> Now I'm trying to add my new Component in a new Feature. >> The problem is that I can't figure out where to add my Feature. >> At the moment, I have only one Feature, and this Feature should >> always be installed. >> The Feature I'd like to add should also always be installed. >> I tried adding it as a new Feature at the same level as the first >> Feature, and I also tried adding it as a new leaf in the first Feature. >> None of these configurations get my new feature to be installed. It >> seems that I can't install the new Feature. >> Here are the confs I tried: >> >> #1: >> <Feature Id='Complete' Level='1'> >> <..... a bunch of existing components ....> >> </Feature> >> <Feature Id='Complete2' Level='1'> >> <ComponentRef Id='MY_NEW_COMPONENT' /> >> </Feature> >> >> #2: >> <Feature Id='Complete' Level='1'> >> <..... a bunch of existing components ....> >> <Feature Id='Complete2' Level='1'> >> <ComponentRef Id='MY_NEW_COMPONENT' /> >> </Feature> >> </Feature> >> >> Any ideas? >> >> Thanks again for your help. >> >> Fred >> >> Rob Mensching a écrit : >> >>> I think the MSI SDK on "Minor Upgrades" confirms your observations: >>> >>> A minor upgrade can be used to add new features and >>> components but cannot reorganize the feature-component tree. >>> >>> You'll need to add the new Components to a new Feature. >>> >>> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] On Behalf Of >>> Frédéric Viollet >>> Sent: Thursday, April 24, 2008 06:30 >>> To: wix-users@lists.sourceforge.net >>> Subject: [WiX-users] adding a component on a minor upgrade >>> >>> Hi everyone, >>> >>> Is it possible to add a component to an installed feature through a >>> minor upgrade? >>> The component I'm trying to add contains two files. And it seems, by >>> the >>> behavior I'm experiencing, that the answer is *no*. >>> Could someone confirm this? >>> >>> Point #1: The product, to which I'd like to add a component, upgrades >>> well if I don't add the component... >>> >>> Point #2: If I try to add the component, I get the following behavior: >>> the product upgrades without apparent errors. However, none of the >>> files >>> are updated, the "Add/Remove Programs" is updated with the new version >>> name. And when I try to uninstall the upgraded version, the entry in >>> "Add/Remove Programs" is removed *but* none of the files/services are >>> removed. >>> >>> Point #3: Strangely, I have another product in which I already had >>> added >>> a Component in an installed feature without any problem. The only >>> difference, is that the component I added only contained any entry >>> <CreateFolder > (no Files) >>> >>> Thanks for your help. >>> >>> Fred >>> >>> ------------------------------------------------------------------------- >>> >>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >>> Don't miss this year's exciting event. There's still time to save $100. >>> Use priority code J8TL2D2. >>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >>> >>> >>> _______________________________________________ >>> 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 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save >> $100. Use priority code J8TL2D2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >> >> >> _______________________________________________ >> 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 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
