Yes, that's the approach my team and I concluded to last night... to stop having a 32-bit package for the 32-bit components and a 64-bit package for the 64-bit components. Leave the 32-bit components in the 32-bit package, but stop it installing on 64-bit and duplicate it's core elements in the 64-bit package for the 64-bit operating systems - thus acheiving both variations of the software in one tidy package.
Although, for files that are used by both variations, do you use the DuplicateFile table? I've not used that before and think it'll be more efficient than including some elements twice. My main concern is that you'd have to have the source component installed for the duplicates to exist, or can you have either? Cheers, G -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Should-you-install-32-bit-and-64-bit-versions-os-the-same-application-tp7578776p7578809.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
