MikeR wrote: > > 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. >
Yes - that's what I'm doing. The problem is that the property [TOMCATHOME] passed through a CustomActionData property shows up in the script as the string "[TOMCATHOME]". It only gets evaluated when the script passes it on to some other function. Thanks for the tip about scripts in installers. Will keep that in mind when we have the opportunity to re-write our installer :-) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Evaluate-property-tp5165399p5167850.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
