There are only three possible "solutions":
1) use a better MSM. Unfortunately there isn't one from MSFT at this time.
Hopefully they will improve their MSMs over time.
2) use a bootstrapper that installs the runtime for you using their .exe
file (vcredist*.exe) for the runtime.
3) live with these warnings.

#2 has the disadvantage that the runtime can be removed from the computer by
the user independently of your application, which will most likely break
your application.

Some people suppress validation in light.exe and use smoke.exe to run
validation separately, processing the warnings independently of their build
results.

-----Original Message-----
From: Vova Froimchuk [mailto:vova.fr...@gmail.com] 
Sent: Monday, October 26, 2009 6:45 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Linkage warnings when using CRT merge modules.

My code is quite standard way to include merge files:

*    <DirectoryRef Id="TARGETDIR">*
*      <Merge Id="CRTredist" *
*
SourceFile="$(var.MergeModulesDir)\Microsoft_VC80_CRT_x86.msm" *
*             DiskId="1" Language="0"/>*
*      <Merge Id="CRTredistPolicy"*
*
SourceFile="$(var.MergeModulesDir)\policy_8_0_microsoft_vc80_crt_x86.msm"*
*             DiskId="1" Language="0"/>     *
*    </DirectoryRef>*
*   *
*    <Feature Id="ProductFeature" Level="1">      *
*      <MergeRef Id="CRTredist" />*
*      <MergeRef Id="CRTredistPolicy" />*
*    </Feature>*

I get like a hundred+ different warnings (which, well, worry me a bit,
although the install seems to
work.) The examples of warnings I get are as following:

warning LGHT1055: The InstallExecuteSequence table contains an action
'SxsInstallCA' which cannot be merged from the merge module 'C:\Program
Files\Common Files\Merge Modules\policy_8_0_microsoft_vc80_crt_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.
warning LGHT1055: The InstallExecuteSequence table contains an action
'SxsUninstallCA' which cannot be merged from the merge module 'C:\Program
Files\Common Files\Merge Modules\policy_8_0_microsoft_vc80_crt_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.

warning LGHT1076: ICE03: String overflow (greater than length permitted in
column); Table: Component, Column: KeyPath, Key(s):
downlevel_payload.8.0.50727.4053.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E

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.

 warning LGHT1076: ICE82: This action
SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E has duplicate sequence
number 1 in the table InstallExecuteSequence

warning LGHT1076: ICE82: This action
SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E has duplicate sequence
number 4 in the table InstallUISequence

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

Now, as I understood after some long and frustrating research many people
encountered the problem, but I yet have seen any solution. Thanks in advance
for any help.
----------------------------------------------------------------------------
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to