Phil, Not sure if you have hit on something here. Based on some reading on the "MajorUpgrade" element and various readings about subtopics we ran across something odd. According to Orca there is no MigrateFeatureStates action in the InstallExecuteSequence table of the MSIs built in WiX 3.8.1128.0. We are now wondering if the WiX 2.0.5805.0 constructs regarding upgrades, while they compile and link, don't work in 3.8.1128.0 since similar compile and link in WiX 2.0.5805.0 do have a MigrateFeatureStates action.
dave williamson -----Original Message----- From: Dave Williamson, Clear Sky Software [mailto:d...@clearskysoftware.com] Sent: Thursday, December 12, 2013 4:11 PM To: 'General discussion about the WiX toolset.' Subject: RE: [WiX-users] Condition logic Ah. I see there is a "MajorUpgrade" element in WiX now. That is not what I meant to convey when stating "major upgrade". A new something to check out though. In this case we are using the following: <Property Id="NEWERPRODUCTFOUND" Secure="yes" /> <Property Id="PREVIOUSVERSIONSINSTALLED" Secure="yes" /> <Upgrade Id="GUID-HERE"> <UpgradeVersion Minimum="3.0.5064" Property="NEWERPRODUCTFOUND" OnlyDetect="yes" IncludeMinimum="yes" /> <UpgradeVersion Minimum="3.0.0" Maximum="3.0.5064" Property="PREVIOUSVERSIONSINSTALLED" IncludeMaximum="no" /> </Upgrade> dave williamson -----Original Message----- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Thursday, December 12, 2013 11:59 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Condition logic It's possible that the major upgrade is migrating feature states. This does not seem to explain the issue, although migrating feature states seems to be what you want to happen, and that wouldn't need a registry search to detect previously installed features. However, migrating feature states is one of the things that prevents the Condition table from being used. So if there is anything in your install that says that a component or feature needs to be installed then the Condition table won't be used. http://msdn.microsoft.com/en-us/library/aa368014(v=vs.85).aspx and see Preselected. Phil Wilson On Thu, Dec 12, 2013 at 5:51 AM, Dave Williamson, Clear Sky Software < d...@clearskysoftware.com> wrote: > Nicolás, > > Good point. In all three scenarios the feature comes up selected to > install. > > > For Scenario 1 this is expected. (new install) > > For Scenario 2 this is unexpected. (major upgrade install where feature > was NOT previously installed) > > For Scenario 3 this is expected. (major upgrade install where feature was > previously installed) > > > Since the Property HAVELS2208 is null in scenario 2, I tried an > alternative of > > <Property Id='HAVELS2208' Value='0'> > > And also made the Condition evaluation more explicit > > <Condition Level='1'><![CDATA[(Installed AND HAVELS2208=1) OR (NOT > Installed)]]></Condition> > > Still no dice. > > > I'm missing the obvious. > > > For scenario 2 the log file shows > > AppSearch: Property: HAVELS2208, Signature: registrysearchHAVELS2208 > MSI (c) (64:28) [08:43:46:321]: Note: 1: 2262 2: Signature 3: -2147287038 > MSI (c) (64:28) [08:43:46:321]: Note: 1: 1402 2: > HKEY_LOCAL_MACHINE\Software\ABC\DEF\LS2208 3: 2 > > > Using Orca the MSI clearly has a condition of > > LS2208Feature > 1 > (Installed AND HAVELS2208=1) OR (NOT Installed) > > I remain baffled. > > dave williamson > > > > > -----Original Message----- > From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] > Sent: Wednesday, December 11, 2013 5:07 PM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] Condition logic > > 2013/12/11 Dave Williamson, Clear Sky Software <d...@clearskysoftware.com > >: > > My brain is twisted and can't seem to get the condition logic right. > > > > 1. If the Product has not been installed on the machine then the > > condition should set Level to 1. > > > > 2. If the Product has been installed but the HAVELS2208 registry > key > > doesn't exist then the condition should NOT set Level to 1. > > > > 3. If the Product has been installed and the HAVELS2208 registry > key > > does exist then the condition should set Level to 1. > > > > For some reason I can't seem to create the right logic in the condition > to > > evaluate as expected for the above 3 scenarios. > > > > Can someone show me what I'm doing wrong? > > I don't see anything obviously wrong with your code; but you only > described the expected behavior. What is the wrong actual behavior > you're seeing? > > -- > Nicolás > > > ---------------------------------------------------------------------------- -- > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > ---------------------------------------------------------------------------- -- > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ---------------------------------------------------------------------------- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
