Correction: By default a CA is run twice if you put it in both sequences and
UILevel is NOT "basic" NOR "silent".
;)
zett42 wrote:
>
>
> Robert O'Brien-2 wrote:
>>
>> Question - is the reason for sequencing the execution of a customaction
>> in both InstallUISequence And InstallExecuteSequenc
Robert O'Brien-2 wrote:
>
> Question - is the reason for sequencing the execution of a customaction in
> both InstallUISequence And InstallExecuteSequence so that you cover both
> interactive and unattended installs?
>
Exactly.
Robert O'Brien-2 wrote:
>
> In the case of an interactive instal
04, 2008 10:25 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] prerequisite conditions
http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx
Under "Feature and component state values".
I think it could work if you put LaunchConditions after CostFinalize in the
sequen
In article <[EMAIL PROTECTED]>,
Robert O'Brien <[EMAIL PROTECTED]> writes:
> Is it expected that prerequisite condition statements support checking
> featur e state and action values in order to determine if prerequisite
> should be check ed for, e.g. is the following valid given an msi that
http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx
Under "Feature and component state values".
I think it could work if you put LaunchConditions after CostFinalize in the
sequence tables.
Otherwise, you could also use a CustomAction using the "Error" attribute and
you could sequence thi
5 matches
Mail list logo