Feature (and Component) states aren't available/defined until after 
CostFinalize.  That's what usually bites.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing 
Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 
|jocoo...@jackhenry.com



-----Original Message-----
From: Tony [mailto:yellowjacketl...@gmail.com] 
Sent: Wednesday, October 29, 2014 12:06 PM
To: WiX Users
Subject: [WiX-users] Defining proper 'condition' for an action..

I have an action in the execute sequence that I want to run during full 
install, full uninstall and when 'MyFeature' is being installed or uninstalled.

I thought...

'&MyFeature<>-1 AND !MyFeature<>&MyFeature'

...would work, but on a full product uninstall, the 'per feature'
properties don't seem to get evaluated.

Maybe &MyFeature<>-1 OR REMOVE=ALL would be a better option?

I don't need to support upgrades.  But I do need to support Modify/Change.

--
Tony
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.


------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to