On 07-Sep-11 12:42, john.burak wrote:
> I'm also curious why WixUI_Advanced needs to put anything in
> InstallExecuteSequence, where Mondo does not. Both dialog sets allow
> the same basic functionality.
WixUI_Advanced supports per-user and per-machine scope selection; none
of the other dialog
Bob Arnson-6 wrote:
>
> WixUI_Advanced is the only dialog set that includes something in
> InstallExecuteSequence. So it pulls in some values that conflict with
> the bad sequences from the merge module.
>
If the merge modules alone (without the Advanced UI) don't produce these ICE
validation
On 06-Sep-11 13:51, john.burak wrote:
> I'm curious why sequencing was altered by the Advanced UI + particular merge
> modules. With Mondo the sequence numbers were correct even with the same
> merge modules. If this might be a bug in the Advanced UI let me know there
> is anything you'd like me
Thanks, that seems to have worked.
I'm curious why sequencing was altered by the Advanced UI + particular merge
modules. With Mondo the sequence numbers were correct even with the same
merge modules. If this might be a bug in the Advanced UI let me know there
is anything you'd like me to test.
Sounds like the Merge Modules are broken, most likely around their
"Before/After" sequencing. One thing you might try is adding those actions
to your .wxs InstallExecuteSequence without sequence numbers. Something
like:
The WiX toolset will put the values in with the default (aka: correct)
I've successfully I added the "WixUI_Advanced" UI to my installer and it
works. But now I get these errors:
Error 293 ICE27: 'StopServices' Action in InstallExecuteSequence table in
wrong place. Current: Costing, Correct: Execution light.exe 0
1
Error 294 ICE27: Act
6 matches
Mail list logo
