Thanks bob, I understand how to make them secure, but how do one make a
property public?
Regards,
Tobias
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: den 26 februari 2007 17:03
To: Tobias Bengtsson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Propertys read in with RegistrySearch,
manipulated after that in the UI
Tobias Bengtsson wrote:
Which action evaluates which features to be installed?
CostFinalize
In my different features I use conditions to decide what to be installed
or not (<Condition Level="1">NAME = "test"</Condition>, installed If
NAME=test), and depending on if the property gets set with a
RegistrySearch or in my own UI, I get different results,
You can't use properties set from the UI in feature conditions unless
you make them public and secure, so they get passed from the UI sequence
to the Execute sequence. Registry searches get set during AppSearch,
which WiX schedules before CostFinalize, so that's why it shows up the
second time.
--
sig://boB
http://bobs.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
