If you only have access to CustomActionData then I'm assuming your custom action is scheduled for deferred mode. You don't get general property access during a deferred custom action. You need to write an accompanying immediate-mode custom action that stores all the data required into a property named to match your deferred-mode custom action name. Then you can access that data via the CustomActionData property in your deferred mode custom action.
I'd recommend using DTF custom actions as it has a nice framework around passing data via CustomActionData, as well as a lot of other nice features for CA authoring. Though using DTF for your CAs will bring on a .NET dependency so if your app doesn't require .NET you may want to stick to C++ custom actions. I only suggest that because script-based custom actions can be problematic, here's some info on why - http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.aspx -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Evaluate-property-tp5165399p5167809.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
