PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard
Sent: Friday, September 05, 2008 3:00 PM
To: WiX Users
Subject: Re: [WiX-users] Property problem - additional info
In article <[EMAIL PROTECTED]>,
Mike Rerick <[EMAIL PROTECTED]> writes:
> I have set all of the needed propert
Yes, all of the problem property Ids are in uppercase.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard
Sent: Friday, September 05, 2008 3:00 PM
To: WiX Users
Subject: Re: [WiX-users] Property problem - additional info
In article <[EM
In article <[EMAIL PROTECTED]>,
Mike Rerick <[EMAIL PROTECTED]> writes:
> I have set all of the needed properties to have the Secure="yes" attribute.
> The install is a perMachine install on XP. The properties do appear in the
> SecureCustomProperties property in the properties list that the
Arnson
Sent: Friday, September 05, 2008 8:45 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Property problem - additional info
Mike Rerick wrote:
> It appears that in the InstallExecuteSequence, all of the various global
> properties that had th
Take a look at the SecureCustomProperties Property too.
Cheers,
James
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian
Simoneau
Sent: 05 September 2008 16:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Property
Mike Rerick wrote:
> It appears that in the InstallExecuteSequence, all of the various global
> properties that had their values modified in the InstallUISequence have
> reverted back to having whatever default value they had initially when they
> were declared.
>
Properties have to be public
Run your custom actions to set the properties in the
InstallExecuteSequence as well. Your installer may not run with the UI
anyways.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Rerick
Sent: Thursday, September 04, 2008 6:29 PM
T
7 matches
Mail list logo
