Kelly Summerlin wrote: > So it sounds like here that I should have separate GUIDs for 32-bit and > 64-bit <component> definitions even though the assemblies that are being > deployed are exactly the same. If this is the case, then I can > understand the need for separate GUIDs, but it sure makes maintaining > 32-bit and 64-bit installs twice as much work. Do I need to have dual > copies of my <component> definitions for 32 & 64 bit?
Pretty much.. that's what I do - maintain parallel trees for the (otherwise identical) 32bit and 64bit installers. I don't use separate GUIDs simply because the maintenence of the trees is already enough overhead (ie. they're out of sync at the moment and I need to schedule some time to work through them). I believe it's an MSI limitation rather than a wix one, but it would be nice if the default changed depending on package type rather than being hardcoded to win32.. going through 500 components copy/pasting "win64" into all of them is a real drag. Tony ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
