I finally got around to working on this issue again. I started with a simple wix project with a similar feature tree as our real install. It worked. So, I started digging around our install and uncovered a custom action (of course!) that did not correctly handle 'modify/change' (which makes sense as we never had modify enabled until now).
The custom action has been corrected and now the installer behaves as expected. On Fri, Sep 12, 2014 at 11:23 AM, Tony <yellowjacketl...@gmail.com> wrote: > It should be noted that in the failure case the feature table reads like > I'd expect...(from the installer log) > > Feature: Root; Installed: Local; Request: Null; Action: Null > Feature: WebSites; Installed: Local; Request: Null; Action: Null > Feature: Public; Installed: Local; Request: Null; Action: Null > Feature: Private; Installed: Local; Request: Absent; Action: Absent > Feature: Tools; Installed: Absent; Request: Local; Action: Local > Feature: ToolA; Installed: Absent; Request: Local; Action: Local > Feature: ToolB; Installed: Absent; Request: Null; Action: Null > > On Fri, Sep 12, 2014 at 11:02 AM, Tony <yellowjacketl...@gmail.com> wrote: > >> I'm updating one of our installers to support change/modify and I'm >> running into a few issues that I don't understand. I'm using the >> WixUI_FeatureTree sequence. And, for the first time installation, by >> default, we want none of the features selected for install. This works. >> However, later during a 'change' sequence in which we add an additional >> feature AND select one feature for uninstall we end up with NO features >> installed on disk. Why is this happening? >> >> More details... >> >> RootFeature >> --WebSites >> ----Public >> ----Private >> --Tools >> ----Tool-A >> ----Tool-B >> >> For my initial fresh install, I choose to only install 'Public". That >> works fine. Later I select "Change" in Programs/Feature and 'add' >> Private. Again, this works as expected. However, when I choose 'Change' a >> third time, I mark Private for uninstall and mark Tool-A for install, the >> end result is *ALL* of the features are removed from *DISK*. Though >> entering the Change a fourth time, it appears as though Windows thinks >> Public and Tool-A are installed. >> >> >> Full Feature code (though some of the fluff removed for brevity): >> <Feature Id="RootFeature" >> Level="2" >> ConfigurableDirectory="MYROOTDIR" >> InstallDefault="local" >> AllowAdvertise="no" > >> <ComponentGroupRef Id="LogsFolderComp"/> >> <FeatureRef Id="WebSites"/> >> <FeatureRef Id="Tools"/> >> </Feature> >> >> <Feature Id="WebSites" >> Level="1" >> InstallDefault="local" >> AllowAdvertise="no" > >> <Feature Id="Private" >> Level="1" >> InstallDefault="local" >> AllowAdvertise="no" > >> <ComponentGroupRef Id="PrivateComp"/> >> </Feature> >> <Feature Id="Public" >> Level="1" >> InstallDefault="local" >> AllowAdvertise="no" > >> <ComponentGroupRef Id="PublicComp"/> >> </Feature> >> </Feature> >> >> <Feature Id="Tools" >> Level="1" >> InstallDefault="local" >> AllowAdvertise="no" > >> <Feature Id="Tool-A" >> Level="1" >> InstallDefault="local" >> AllowAdvertise="no" > >> <ComponentGroupRef Id="ToolAComp"/> >> </Feature> >> <Feature Id="Tool-B" >> Level="1" >> InstallDefault="local" >> AllowAdvertise="no" > >> <ComponentGroupRef Id="ToolBComp"/> >> </Feature> >> </Feature> >> >> -- >> Tony >> > > > > -- > Tony > -- Tony ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
