That fixed it, thanks Bob.
As a comment:
Isn't it unusual convention to have the case of a name dictating the
protection level? I guess that's a legacy thing from MSI, rather than a
feature of WiX..?
On 29/05/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Rik wrote:
> I am creating an installer that has a UI that allows the user to enter
> some values. These values are subsequently used in a custom action as
> part of the actual installation.
Properties must be public (i.e., named in all UPPERCASE) and secure
(@Secure="yes") to be passed from the UI sequence to the execute sequence.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
