1.  Dependency failure:  This warning is telling you that you have a Merge 
Module that depends on another Merge Module but you did not include the second 
Merge Module.  I don't know much about the new ATL Merge Modules, but it would 
appear the core Merge Module requires a second policy module.  You probably 
want to fix this one.

2.  Collision failure:  This warning is telling you that the two Merge Modules 
contain the same CustomAction name but only one of the CustomActions is being 
included.  I happen to know how this CustomAction came about (argued that they 
should create it for a long time) and you can safely ignore this warning.  It 
is lame and I'm sorry.

3.  Duplicate sequence:  This warning is telling you that you have two (or 
more) CustomActions all trying to run at the same time.  The order of execution 
is non-deterministic.  You will get this when merging in a couple Modules that 
all have a bunch of standard directories in them due to the way that 
mergemod.dll handles these things.  This is also pretty lame but this 
particular instance of the warning can be safely ignored because it doesn't 
matter what order these CustomActions run.


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christer 
Solskogen
Sent: Friday, October 27, 2006 00:03
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Merge modules again...

I'm trying to understand how merge modules work. The MSI file is
created, but light produces some warnings I dont understand.

For instance:

light.exe : warning LGHT1076 : ICE25: Possible dependency failure as we
do not find [EMAIL PROTECTED] v in
ModuleSignature table

D:\devel\Era3D\wix\Era3D.wxs(52) : warning LGHT1055 : The
InstallExecuteSequence table contains an action 'SxsUninstallCA' which
cannot be merged from the merge module
'wix\merge/Microsoft_VC80_MFC_x86.msm'.  This action is likely colliding
with an action in the database that is being created.  The colliding
action may have been authored in the database or merged in from another
merge module.  If this is a standard action, it is likely colliding due
to a difference in the condition for the action in the database and
merge module.  If this is a custom action, it should only be declared in
the database or one merge module.

light.exe : warning LGHT1076 : ICE82: This action
SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E has duplicate sequence
number 1 in the table InstallExecuteSequence

How do I resolve those issues?

I've only added this to my wxs:
...
<Merge Id='VC80_MFC' SourceFile='merge/Microsoft_VC80_DebugMFC_x86.msm'
DiskId='1' Language='1033' />
<Merge Id='VC80_ATL' SourceFile='merge/Microsoft_VC80_ATL_x86.msm'
DiskId='1' Language='1033' />
...

<Feature...>
...
<MergeRef Id='VC80_ATL' />
<MergeRef Id='VC80_MFC' />
...
</Feature>


--
chs


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to