> It doesn't evaluate correctly until after the CostFinalize action.
When does that happen?
My experience is that the &Feature property is correct in the following
dialog boxes. I use that in my install sequence to skip a dialog box if
the corresponding feature is not selected, as demonstrated in my
"Beginner's Tutorial", on this page:
http://www.merlinia.com/mdt/WiXTutorial4.msl
"Making the display of a dialog box dependent on features selected"
Rennie
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: 26. april 2007 23:55
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Check for at least one required
feature?
It doesn't evaluate correctly until after the CostFinalize
action.
Phil Wilson
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Parker
Sent: Thursday, April 26, 2007 2:37 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Check for at least one required
feature?
So then is it correct to say that &FEATURE doesn't evaluate to
anything during the UI Sequence? Or do I have my Publish actions below
screwy?
Here's an example: In my main Installer .wxs file I have...
<Feature Id="FEATUREAAA" Level="1" >
Then in a secondary file dialogs.wxs on a Next button I have
<Publish Event="NewDialog"
Value="AAADialog"><![CDATA[&FEATUREAAA = 3]]></Publish>
<Publish Event="NewDialog" Vaue="NormalDialog">1</Publish>
It ALWAYS goes to NormalDialog regardless of whether or not I
select FEATUREAAA in the customization step earlier in the UI sequence.
Any thoughts or help? Thanks,
-Scott
On 4/26/07, Scott Parker <[EMAIL PROTECTED]> wrote:
Sorry if this is essentially a repost, but I couldn't
find anything on wix-users asking quite the same question I am.
Our product consists of FeatureAAA and FeatureZZZ. We
need to enforce that the user has selected at least either FeatureAAA or
FeatureZZZ to install. I've tried using a Publish - SpawnDialog to throw
an error as well as a Condition to disable the control like those used
in the LicenseAgreementDlg, both trying to tie into "&FeatureAAA <> 3
AND &FeatureZZZ <> 3" with no luck. My guess as to why that happens is
that perhaps the features aren't set to their new states until after
this dialog has been processed, but that's a total guess.
Is there a better (or any) way I should be doing this?
Thanks,
-Scott
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
