Hi all, I am currently writing an installer that needs to install both Visual Studio 2005 AND 2008 C Runtime Libraries. The reason is that some of the binaries I have to install (PostgreSQL) are built with Visual Studio 2005, and my own binaries are built with Visual Studio 2008. Everything must be installed easily with one installer, hence why I am handling the PostgreSQL install in my own installer.
The problem is when I try and use the merge modules for both runtime libraries, I get the warnings listed at the bottom of this post. When I run the installer, all seems to go okay so maybe there isn't a problem, though the test machine is not currently clean so it might just seem okay. I'm going to wipe the test machine and give it another try, but either way I thought it prudent to check with others if there could be any potential issues, and to see if there is perhaps a better way of doing all of this. I did try just running the setup for the redistributable installs from my installer, but then I got errors about not being able to run multiple msi installs, etc.... Warnings listed below .. thanks! 2>V:\opal\clients\monika\project\installer\Product.wxs(119,0): warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsInstallCA' which cannot be merged from the merge module 'files\runtime80\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. 2>V:\opal\clients\monika\project\installer\Product.wxs(119,0): warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsUninstallCA' which cannot be merged from the merge module 'files\runtime80\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. 2>V:\opal\clients\monika\project\installer\Product.wxs(120,0): warning LGHT1055: The InstallExecuteSequence table contains an action 'AllocateRegistrySpace' which cannot be merged from the merge module 'files\runtime90\Microsoft_VC90_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. 2>V:\opal\clients\monika\project\installer\Product.wxs(120,0): warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsInstallCA' which cannot be merged from the merge module 'files\runtime90\Microsoft_VC90_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. 2>V:\opal\clients\monika\project\installer\Product.wxs(120,0): warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsUninstallCA' which cannot be merged from the merge module 'files\runtime90\Microsoft_VC90_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. 2>V:\opal\clients\monika\project\installer\Product.wxs(121,0): warning LGHT1055: The InstallExecuteSequence table contains an action 'AllocateRegistrySpace' which cannot be merged from the merge module 'files\runtime90\policy_9_0_Microsoft_VC90_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. 2>V:\opal\clients\monika\project\installer\Product.wxs(121,0): warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsInstallCA' which cannot be merged from the merge module 'files\runtime90\policy_9_0_Microsoft_VC90_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. 2>V:\opal\clients\monika\project\installer\Product.wxs(121,0): warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsUninstallCA' which cannot be merged from the merge module 'files\runtime90\policy_9_0_Microsoft_VC90_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. Mark. -- ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
