On 5/26/2010 12:14 PM, Nick Ramirez wrote:
> Anyone know more about the -1 action state during the UI portion?
>
http://www.joyofsetup.com/2008/04/09/feature-states-in-component-conditions/
--
sig://boB
http://joyofsetup.com/
Typically, if a component depends on a feature, it is simply included as
part of that feature.
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Wednesday, May 26, 2010 9:55 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Component with feature
Okay. I think I understand this a bit more now. I think that the action state
of components and features are figured out during the FileCost phase, but
not set in stone and made available until after CostFinalize. Also, I
believe that conditions on components and features are evaluated at the same
The action state of a featre is supposedly set after CostFinalize. Trying it
out, it seems that checking the action state in the condition of a
component, as you've done here, evaluates to -1, "unknown".
I would have thought that it would always evaluate to 3, "local", since the
INSTALLLEVEL pro
fice - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Rory Primrose [mailto:r...@neovolve.com]
Sent: 26 May 2010 06:25
To: WiX Mail List (wix-users@lists.sourceforge.net)
Subject: [WiX-users] Component with feature condition not actioned
Hi guys,
I'm having an issue with components with feature conditions not being actioned.
My feature tree is:
The installer is intended to configure a web.config connection string for the
first installation
6 matches
Mail list logo
