Rob Mensching wrote:
> It has been a long time since we found a dependency between tables that
> wasn't automatically added by the WiX toolset. Is it possible that a
> ControlCondition table is required by the ICEs whenever there is a Dialog
> table... or something screwy like that?
>
Apparentl
It has been a long time since we found a dependency between tables that
wasn't automatically added by the WiX toolset. Is it possible that a
ControlCondition table is required by the ICEs whenever there is a Dialog
table... or something screwy like that?
On Fri, Nov 27, 2009 at 3:41 PM, Bob Arnson
Rob Hamflett wrote:
> Yes, but why? It used to work fine without it.
Did you have a ControlCondition table? The ICEs come from the MSI team
so we have to rely on the doc for the hows/whys.
--
sig://boB
http://joyofsetup.com/
Yes, but why? It used to work fine without it. In addition to the EndDialog
event I previously had
a Custom Action that was launched when that button was clicked. I removed the
Custom Action and the
problem started appearing. There wasn't a Condition on the Control to begin
with (although
Rob Hamflett wrote:
> ICE17 FAILICE Internal Error 105. API Returned: 1615.
> ICE17 FAILError 2228: C:\DOCUME~1\Robert\LOCALS~1\Temp\ICEA37.tmp,
> ControlCondition, SELECT
> `Dialog_`,`Control_` FROM `ControlCondition` WHERE `Dialog_`=? AND
> `Control_`=? AND `Action`= 'Enable'
>
222
There seems to be an issue with how some UI elements are processed that results
in an ICE validation
failure. In Orca the 2 errors reported are:
ICE17 FAILICE Internal Error 105. API Returned: 1615.
ICE17 FAILError 2228: C:\DOCUME~1\Robert\LOCALS~1\Temp\ICEA37.tmp,
ControlCondition
6 matches
Mail list logo
