Turns out this wasn't specifically the problem.

But when I put the @Secure attribute on the Property definitions, the
Compiler told me that the Property names have to be all uppercase before
they can be made public.  Guess, I'd missed this little syntactical jewel.

Now that I've up-cased all the relevant Property names, it's working fine.

Many thanks for bailiing me out of this self-imposed deadend....

-pbm



Bob Arnson-6 wrote:
> 
> pbm wrote:
>> This is a child of the <product ... > element.  And here the Property
>> values
>> are resolved to their original default settings rather than to the new
>> values that were input by the user in the Config Dialog.
>>   
> 
> Make sure your <Property> elements have the @Secure="yes" attribute, to
> ensure it's passed from the UI to the execute sequence.
> 
> 
> -- 
> sig://boB
> http://joyofsetup.com/
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Wix-Property-Values-tf4208227.html#a12015809
Sent from the wix-users mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to