[WiX-users] Best Way to Include MSVCRT 80 Dependencies
What's the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I've tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: ** !-- MSVCRT 80 libraries -- ?if $(env.BUILDTYPE) = debug? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / ?else? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\microsoft_vc80_crt_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / ?endif? InstallExecuteSequence FindRelatedProducts Before=LaunchConditions / RemoveExistingProducts After=InstallValidate / /InstallExecuteSequence InstallUISequence FindRelatedProducts Before=LaunchConditions / /InstallUISequence UI UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchBrowser Order=1![CDATA[UILevel 2 AND NOT Installed]]/Publish /UI Feature Id=MyFeature Title=My Feature Level=1 MergeRef Id=CRT / MergeRef Id=CRT Policy / !-My Components -- /Feature /Feature * When I compile this I get a bunch of Warnings (see below). Any suggestions on how to fix? Thx. Steve Bush *** 1Compiling - Candle (v3.0.2512.0) .\MyfeatureSetup.wxs MyfeatureSetup.wixobj 1Building - Light (v3.0.2512.0) - objd\i386\MyfeatureSetup.msi ... 1warnings in directory d:\clues\private\setup\myfeaturesetup 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsInstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.Debu CRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the datab se that is being created. The colliding action may have been authored in the database or merged in from anot er merge module. If this is a standard action, it is likely colliding due to a difference in the condition f r 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. 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsUninstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.De ugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the dat base that is being created. The colliding action may have been authored in the database or merged in from an ther 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 t e database or one merge module. 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
IMHO: statically link against libcmt so you don't have the dependency. smile/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Bush Sent: Friday, June 29, 2007 9:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Best Way to Include MSVCRT 80 Dependencies What's the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I've tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: ** !-- MSVCRT 80 libraries -- ?if $(env.BUILDTYPE) = debug? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / ?else? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\microsoft_vc80_crt_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / ?endif? InstallExecuteSequence FindRelatedProducts Before=LaunchConditions / RemoveExistingProducts After=InstallValidate / /InstallExecuteSequence InstallUISequence FindRelatedProducts Before=LaunchConditions / /InstallUISequence UI UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchBrowser Order=1![CDATA[UILevel 2 AND NOT Installed]]/Publish /UI Feature Id=MyFeature Title=My Feature Level=1 MergeRef Id=CRT / MergeRef Id=CRT Policy / !-My Components -- /Feature /Feature * When I compile this I get a bunch of Warnings (see below). Any suggestions on how to fix? Thx. Steve Bush *** 1Compiling - Candle (v3.0.2512.0) .\MyfeatureSetup.wxs MyfeatureSetup.wixobj 1Building - Light (v3.0.2512.0) - objd\i386\MyfeatureSetup.msi ... 1warnings in directory d:\clues\private\setup\myfeaturesetup 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsInstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.Debu CRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the datab se that is being created. The colliding action may have been authored in the database or merged in from anot er merge module. If this is a standard action, it is likely colliding due to a difference in the condition f r 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. 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsUninstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.De ugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the dat base that is being created. The colliding action may have been authored in the database or merged in from an ther 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 t e database or one merge module. 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
Unfortunately, I'm not in a position to recompile all of the code to remove the CRT dependency. Sometimes you have to play the hand you're dealt. I've done the web searching route and find a lot of conflicting info. Any pointers would be appreciated. From: Rob Mensching Sent: Friday, June 29, 2007 9:27 AM To: Steve Bush; wix-users@lists.sourceforge.net Subject: RE: Best Way to Include MSVCRT 80 Dependencies IMHO: statically link against libcmt so you don't have the dependency. smile/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Bush Sent: Friday, June 29, 2007 9:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Best Way to Include MSVCRT 80 Dependencies What's the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I've tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: ** !-- MSVCRT 80 libraries -- ?if $(env.BUILDTYPE) = debug? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / ?else? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\microsoft_vc80_crt_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / ?endif? InstallExecuteSequence FindRelatedProducts Before=LaunchConditions / RemoveExistingProducts After=InstallValidate / /InstallExecuteSequence InstallUISequence FindRelatedProducts Before=LaunchConditions / /InstallUISequence UI UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchBrowser Order=1![CDATA[UILevel 2 AND NOT Installed]]/Publish /UI Feature Id=MyFeature Title=My Feature Level=1 MergeRef Id=CRT / MergeRef Id=CRT Policy / !-My Components -- /Feature /Feature * When I compile this I get a bunch of Warnings (see below). Any suggestions on how to fix? Thx. Steve Bush *** 1Compiling - Candle (v3.0.2512.0) .\MyfeatureSetup.wxs MyfeatureSetup.wixobj 1Building - Light (v3.0.2512.0) - objd\i386\MyfeatureSetup.msi ... 1warnings in directory d:\clues\private\setup\myfeaturesetup 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsInstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.Debu CRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the datab se that is being created. The colliding action may have been authored in the database or merged in from anot er merge module. If this is a standard action, it is likely colliding due to a difference in the condition f r 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. 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsUninstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.De ugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the dat base that is being created. The colliding action may have been authored in the database or merged in from an ther 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 t e database or one merge module. 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
We just install the redistributables alongside our main exes. Not sure you're allowed to do that for the debug versions, though. Rob Steve Bush wrote: Unfortunately, I’m not in a position to recompile all of the code to remove the CRT dependency. Sometimes you have to play the hand you’re dealt. I’ve done the web searching route and find a lot of conflicting info. Any pointers would be appreciated. *From:* Rob Mensching *Sent:* Friday, June 29, 2007 9:27 AM *To:* Steve Bush; wix-users@lists.sourceforge.net *Subject:* RE: Best Way to Include MSVCRT 80 Dependencies IMHO: statically link against libcmt so you don’t have the dependency. smile/ *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Steve Bush *Sent:* Friday, June 29, 2007 9:04 AM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] Best Way to Include MSVCRT 80 Dependencies What’s the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I’ve tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: ** !-- MSVCRT 80 libraries -- ?if $(env.BUILDTYPE) = debug? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / ?else? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\microsoft_vc80_crt_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / ?endif? InstallExecuteSequence FindRelatedProducts Before=LaunchConditions / RemoveExistingProducts After=InstallValidate / /InstallExecuteSequence InstallUISequence FindRelatedProducts Before=LaunchConditions / /InstallUISequence UI UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchBrowser Order=1![CDATA[UILevel 2 AND NOT Installed]]/Publish /UI Feature Id=MyFeature Title=My Feature Level=1 MergeRef Id=CRT / MergeRef Id=CRT Policy / !—My Components -- /Feature /Feature * When I compile this I get a bunch of Warnings (see below). Any suggestions on how to fix? Thx. Steve Bush *** 1Compiling - Candle (v3.0.2512.0) .\MyfeatureSetup.wxs MyfeatureSetup.wixobj 1Building - Light (v3.0.2512.0) - objd\i386\MyfeatureSetup.msi ... 1warnings in directory d:\clues\private\setup\myfeaturesetup 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsInstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.Debu CRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the datab se that is being created. The colliding action may have been authored in the database or merged in from anot er merge module. If this is a standard action, it is likely colliding due to a difference in the condition f r 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. 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsUninstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.De ugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the dat base that is being created. The colliding action may have been authored in the database or merged in from an ther 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 t e database or one merge module. 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
We just install the redistributables alongside our main exes. Not sure you're allowed to do that for the debug versions, though. The EULA prohibits redistributing the debug versions according to this: http://blogs.msdn.com/nikolad/archive/2005/09/02/running-c-application-b uilt-by-vc-express-on-another-computer.aspx Cheers, John - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
Steve, What's the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I've tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: This blog entry: http://blogs.msdn.com/astebner/archive/2007/02/13/building-an-msi-using- wix-v3-0-that-includes-the-vc-8-0-runtime-merge-modules.aspx documents these various warnings but doesn't go beyond noting that you could disable them, but you would be disabling them for your whole project. I noticed another post on this list recently, where someone had a special verification mode in their project for running ice against, which excluded all merge modules. Cheers, John - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
