If the Components are mutually exclusive, then you can probably get away with the same GUIDs. I personally would start planning to get the GUIDs to be different (auto-guid is ideal) just in case the mutual exclusivity runs out.
On Mon, Feb 7, 2011 at 11:23 AM, Quinton Tormanen <quint...@deltamotion.com>wrote: > We've distributed our application for some time as a 32-bit app, and > then later we added a 64-bit installer to get the 64-bit USB drivers > installed, but still installed our native application as 32-bit (using > WOW64). Now I need to make the 64-bit installer use the 64-bit EXE > (while the 32-bit installer still uses the 32-bit EXE) and I'd like to > do it from a single source (wxs). I'm already using the -arch option, > and have changed the root directory from ProgramFilesFolder to > ProgramFiles64Folder for the 64-bit build. The requirement that I'm a > little puzzled by is the requirement for unique Component GUIDs on the > 32- and 64-bit versions of the components, which I presume is because > I'm moving the install directory base from ProgramFilesFolder to > ProgramFiles64Folder. > > I understand the value of having them being unique, although our > application has a strict condition where only one of the 32- and 64-bit > installers can be installed. But how should this be done most cleanly? I > can't use Id="*" at this point since I've already had our product out > for some time with the existing GUIDs and I assume I don't want to > change those. I have 12 components switching from 32- to 64-bit in the > 64-bit package, so do I just need to conditionally set the IDs for each > (presumably using <?if $(sys.BUILDARCH) = x86 ?> to set local variables > for the GUIDs) or is there a better way? Or is this not really a > requirement in my case? > > I know this subject has been discussed in the past, but couldn't find an > answer to this specific question. > > Thanks for any guidance you guys can provide. > > Quinton Tormanen > Software Engineer > Delta Computer Systems, Inc. > http://www.deltamotion.com > > > > ------------------------------------------------------------------------------ > The modern datacenter depends on network connectivity to access resources > and provide services. The best practices for maximizing a physical server's > connectivity to a physical network are well understood - see how these > rules translate into the virtual world? > http://p.sf.net/sfu/oracle-sfdevnlfb > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
