Pally Sandher wrote:
I had a similar situation last week & recieved a grand total of 1
replies. I've come to the conclusion that using Condition to set the
Level of a Feature doesn't work (at all, as in it's a bug).
It works but when you switch from the UI to the execute sequence, MSI
explici
isclaimer <http://www.iesve.com/disclaimer.html>
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Aaron
Shurts
Sent: 29 May 2007 20:43
To: Lewis Henderson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Disabling features in the CustomizeDlg based on
UIinteraction...
I use this very successfully actually and have not had any problems with
it. My feature declaration looks like this:
The "Condition" tag sets the feature to 1 or 0 based on the presence of
[MY_NEEDED_PROPERTY]. I use this in several different installs and it works
great. For instanc
I had a similar situation last week & recieved a grand total of 1
replies. I've come to the conclusion that using Condition to set the
Level of a Feature doesn't work (at all, as in it's a bug).
I tried to use it to set the Feature Level to either 1001 or 1 (1001
would exclude it from any install a
4 matches
Mail list logo
