As has been mentioned on this list before, properties go just one way
between UI and Execute sequences. It is by apparent design that you can't
change a property (any property) in the execute sequence and pick up that
change in the UI sequence.
-Original Message-
From: John Cooper
Thank you, Bob and Blair.
I moved the Custom element to InstallUISequence like:
InstallUISequence
Custom Action=SetExitDialogOptText Before=ExecuteAction
NOT Installed
/Custom
/InstallUISequence
and the problem was resolved!
On Mon, Jan 30, 2012 at 12:09 AM, Blair os...@live.com
In my main .wxs file that is based on the WixUI_InstallDir dialog set,
I set WIXUI_EXITDIALOGOPTIONALTEXT so that the final dialog
after successful installation has an extra information.
This is done like this:
Wix xmlns=
Product
...
UIRef Id=WixUI_InstallDir /
Property
Read up on the Secure attribute to the Property element in the Wix schema.
Only secure properties are visible in both the UI and Execute sequences.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
On 1/26/12 12:13 PM, John Cooper wrote:
Read up on the Secure attribute to the Property element in the Wix schema.
Only secure properties are visible in both the UI and Execute sequences.
I'm not sure if the security is the problem because I am not seeing the
errors like Ignoring disallowed
On 26-Jan-12 14:37, T. Kuro Kurosaka wrote:
I thought properties named with all uppercase letters are in
global effect, and passed between the server and the client, back and
forth.
It's one-way only, client to server. There's no way to set a property in
the server and have it available for
6 matches
Mail list logo