Re: [WiX-users] Merge modules again...

[Christer S. <ch...@ep...>]

On 27.10.2006 17:03, Rob Mensching wrote:
> 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.
> 
> 

Thanks for you reply, I managed to fix the Dependency problem.
Still I get some other warnings now:

light.exe : warning LGHT1076 : ICE30: The target file 
'ansiatl.dll|ATL80.dll' might be installed in '[SystemFolder]' by two 
different conditionalized components on an LFN system: 
'ansi_atl80.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E' and 
'nosxs.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E'. If the conditions are not 
mutually exclusive, this will break the component reference counting system.
(I get this error twice)

and

light.exe : warning LGHT1076 : ICE83: The keypath for Global Win32 SXS 
Assembly (Component_=uplevel.66332652_9C28_58B1_FF1F_C8B3B9A1E18E) 
SHOULD NOT be it's manifest file for assemblies other than Win32 Policy 
assemblies
light.exe : warning LGHT1076 : ICE83: The keypath for Global Win32 SXS 
Assembly (Component_=uplevel.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E) 
SHOULD NOT be it's manifest file for assemblies other than Win32 Policy 
assemblies
light.exe : warning LGHT1076 : ICE83: The keypath for Global Win32 SXS 
Assembly (Component_=uplevel.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E) 
SHOULD NOT be it's manifest file for assemblies other than Win32 Policy 
assemblies

Also the application does not start, blaming ATL.

This is a cut'n'paste from my wxs-file:
...
<?ifdef release ?>
<Merge Id='CRT' Language='1033' SourceFile='Microsoft_VC80_CRT_x86.msm' 
DiskId='1' />
<Merge Id='MFC' Language='1033' SourceFile='Microsoft_VC80_MFC_x86.msm' 
DiskId='1' />
<?else ?>
<Merge Id='CRT' Language='1033' 
SourceFile='Microsoft_VC80_DebugCRT_x86.msm' DiskId='1'/>
<Merge Id='MFC' Language='1033' 
SourceFile='Microsoft_VC80_DebugMFC_x86.msm' DiskId='1' />
<?endif ?>
<Merge Id='ATL' Language='1033' SourceFile='Microsoft_VC80_ATL_x86.msm' 
DiskId='1' />
<Merge Id='ATL_policy' Language='1033' 
SourceFile='policy_8_0_Microsoft_VC80_ATL_x86.msm' DiskId='1' />
<Merge Id='CRT_policy' Language='1033' 
SourceFile='policy_8_0_Microsoft_VC80_CRT_x86.msm' DiskId='1' />
<Merge Id='MFC_policy' Language='1033' 
SourceFile='policy_8_0_Microsoft_VC80_MFC_x86.msm' DiskId='1' />
...
<MergeRef Id='ATL' />
<MergeRef Id='CRT' />
<MergeRef Id='MFC' />
<MergeRef Id='ATL_policy' />
<MergeRef Id='CRT_policy' />
<MergeRef Id='MFC_policy' />

...

If anyone has a working template for how to include those merge file 
I'll be very happy.
I'm also under the impression that this works as it should in Wix2. All 
of the examples I've seen on the net using these merge files use this code.

-- 
chs