A verbose log file should show you what those Property values are being set to.
On Tue, Apr 10, 2012 at 9:51 AM, AV <arn...@argeweb.nl> wrote: > Hi, > > I'm trying to get Wix 3.5 to handle .NET version checks a bit more > elegantly > than the how-to suggests. > > The following works perfectly, displaying "NOT #1" if it's been installed: > (I altered the CDATA to get it to be displayed) > > <PropertyRef Id="NETFRAMEWORK40FULL"/> > <PropertyRef Id="NETFRAMEWORK20"/> > <PropertyRef Id="NETFRAMEWORKINSTALLROOTDIR"/> > > <Condition Message="This application requires .NET Framework 4.0. > [NETFRAMEWORK40FULL]"> > <bang[CDATA[NETFRAMEWORK40FULL]]> > </Condition> > > <Condition Message="This application requires .NET Framework 4.0. NOT > [NETFRAMEWORK40FULL]"> > <bang[CDATA[Not NETFRAMEWORK40FULL]]> > </Condition> > > > > When I use this it doesn't work. > I do get the dialog but with only empty property values. > The MsiNetAssemblySupport correctly displays its value. > > <PropertyRef Id="NETFRAMEWORK40FULL"/> > <PropertyRef Id="NETFRAMEWORK20"/> > <PropertyRef Id="NETFRAMEWORKINSTALLROOTDIR"/> > > <UIRef Id="CheckFrameworkTest" /> > > <UI Id="CheckFrameworkTest"> > <Dialog Id="FrameworkDlg4test" Width="260" Height="75" > Title="[ProductName]" NoMinimize="yes" > > > <Control Id="Message4test" Type="Text" X="10" Y="10" Width="240" > Height="40" > Text="dir: [NETFRAMEWORKINSTALLROOTDIR] - v4: > [NETFRAMEWORK40FULL] - v2: [NETFRAMEWORK20] - MsiNetAssemblySupport: > [MsiNetAssemblySupport] " /> > > <Control Id="Cancel4test" Type="PushButton" X="50" Y="52" Width="56" > Height="17" Cancel="yes" Text="Cancel"> > <Publish Event="SpawnDialog" Value="CancelDlg">1</Publish> > </Control> > > > </Dialog> > > <InstallUISequence> > <Show Dialog="FrameworkDlg4test" Sequence="1" /> > </InstallUISequence> > > </UI> > > All properties are suddenly empty. I originally found out when I used > NETFRAMEWORK40FULL in a condition inside the <Show Dialog> and always got > the dialog. > > The wix.chm literally says: "Once the property is referenced you can use it > in any WiX condition statement." so it's got to be possible. > > Does anyone have any clue what I'm doing wrong here? > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Use-NetFxExtension-properties-in-other-conditions-tp7453544p7453544.html > Sent from the wix-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
