Isn't the win64 setting on the component so you need to build a 64bit and a 32 bit version of each merge module (or wixlib). This is easily done with a shared .wxs file and a compilation setting.
I have 32 and 64 bit components all up my build tree just because one package needs a 32 and a 64 bit msi. (another) Dave -----Original Message----- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 30 July 2013 16:54 To: David Connet; General discussion forWindows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Sigh same merge modules just compiled under x86 and x64 Get the error: Error 49 The merge module 'EnterpriseServicesMM_x64' contains a file identifier, 'fil2502525491FAEBF0E0D0ED1FE352E76D.9EFC3F5B_3D47_4233_A162_371DEF5D8E92', that is duplicated either in another merge module or in a File/@Id attribute. File identifiers must be unique. Please change one of the file identifiers to a different value. C:\Dev\ Setup\Services_Setup\Product.wxs 282 1 Services_Setup <Feature Id="MergeModulesX86" Title="Merge modules for 32 bit OS" Level="1" Display="expand" ConfigurableDirectory="DIRECTORY_PATH_SERVICES"> ... <MergeRef Id="ServicesMergeModule"/> <Condition Level="1"> <![CDATA[NOT(VersionNT64) OR $(var.Platform) = "x86"]]> </Condition> </Feature> <Feature Id="MergeModulesX64" Title="Merge modules for 64 bit OS" Level="1" Display="expand" ConfigurableDirectory="DIRECTORY_PATH_SERVICES"> ... <MergeRef Id="ServicesMergeModule_x64"/> <Condition Level="1"> <![CDATA[VersionNT64 OR $(var.Platform) = "x64"]]> </Condition> ... <Merge Id="ServicesMergeModule" DiskId="1" SourceFile="$(env.SharedServices)\Installers\wixlib\ServicesMergeModule.msm" Language="1033"/> ... <Merge Id="ServicesMergeModule_x64" DiskId="1" SourceFile="$(env.SharedServices)\Installers\wixlibx64\ServicesMergeModule.ms m" Language="1033"/> -----Original Message----- From: David Connet [mailto:d...@agilityrecordbook.com] Sent: July-30-13 11:10 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Assign them to a feature and condition the feature. Dave ----- Original Message ----- From: Steven Ogilvie <steven.ogil...@titus.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Cc: Sent: Tuesday, July 30, 2013 7:16 AM Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public The 5 merge modules have <ComponentGroupRef Id="cmpgrp_Log4Net"/> of about 10 wixlibs The files in the MergeModules and WixLibs are built as AnyCPU however since I need to install the services for 64 bit OS and 32 bit OS I need two MSI's one for 32 and one for 64 bit So I am not using any binary files that are specific for 32 bit or 64 bit, I just need to include the MergeModules in 1 product.wxs file The Merge Modules themselves are built x86 and x64 and are located in two different folders... So the question is, HOW do I conditionally install the merge modules based on the OS bitness? Thanks, Steve ----------------------------------------------------------------------------- - Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been marked as Public by Steven Ogilvie on July-30-13 11:53:30 AM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.com. ----------------------------------------------------------------------------- - Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
