Kevin Burton wrote: > Thank you very much. Progress but I think I am running into the second > problem that you mentioned. The documentation states that in order for the > property to be set in the UI phase and passed to the execution phase it has > to be public for Windows XP and Windows 2000. I am not running either XP or > Windows 2000 (I am running Windows Server 2003) but the symptoms seem to be > the same. As I understand it if the property name does not contain lower > case letters then it is public. Right? >
Where did you see that doc? I'm not aware of any UI differences based on OS version, though there are some new things that come with later versions of MSI itself. Anyway, yes, public properties are all in uppercase and you need to mark a public property as secure to support all cases in moving from UI to execute sequences. -- 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
