Using the proprocessor is one part of the solution. But instead of spending hours with Guid gen, use XSLT to generate the new guids for components, as you will need different component codes for different flavors. I have often done this. Get the transform to just copy all of the nodes save for the guid attributes of the components. Use and exension object to spit out a new guid for the guid attribute.
I use .NET xml/xslt, but maybe MSXML can help. A simple COM component you create will do the GUIDS for the extension object. AFAIK, there is no tool to do this. But since WIX is XML, XSLT has often come to the rescue, eliminating the need for hours of grunt work. Regards, agreen. ---- Peter Shirtcliffe <pshirtcli...@sdl.com> wrote: > This may be of help > http://blogs.msdn.com/heaths/archive/2005/10/24/windows-installer-on-64- > bit-platforms.aspx > > -----Original Message----- > From: John Aldridge [mailto:j...@jjdash.demon.co.uk] > Sent: 23 June 2009 15:36 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] 32 & 64 bit installers from common WiX source? > > Are there any guidelines for how best to create both a 32 and a 64 bit > installer from a single WiX source file? I can use variable substitution > to set the Platform attribute and pick up the right versions of the > various executable files, but I'm puzzled about how to manage Component > GUIDs. Do they need to be different for the 32 & 64 bit installers, and > if so does WiX/Votive provide me any tools which can be used to manage > this difference? It is possible that both the 32 and 64 bit versions > will need to be installed at once, if that matters. > > A separate but perhaps related question is how to manage a new product > version which can be installed side-by-side with the current version. My > understanding is that I need to allocate new Component GUIDs, but I'd > rather not spend hours with GUIDGEN copy & pasting hundreds of new > entries! I guess I could write a utility to process a WiX source file > and replace every GUID in it, but is there a better way? > > Apologies if these questions have been answered before: I thought they > might be common problems, but I've done quite a bit of searching and > failed to find answers. > > -- > Thank you for any help, > John > > > ------------------------------------------------------------------------ > ------ > Are you an open source citizen? Join us for the Open Source Bridge > conference! > Portland, OR, June 17-19. Two days of sessions, one day of unconference: > $250. > Need another reason to go? 24-hour hacker lounge. Register today! > http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebrid > ge.org > _______________________________________________ > 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. > > > ------------------------------------------------------------------------------ > Are you an open source citizen? Join us for the Open Source Bridge conference! > Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. > Need another reason to go? 24-hour hacker lounge. Register today! > http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
