Hi Jon, > We currently have a product that is private labeled for multiple customers. > The code is the same, the executables are just renamed and we use some > different graphics. I'm trying to decide the best way to put the install > script together for this.
We have a similar requirement - Live, Test and Training versions of the same product, but installed with different product names, locations, and a few other variables (db/web names). > If I would use the same .wxs file for each build, I know I would need a > different Guid for the product ID, and the upgrade code. Would I need a > different Guid for each component as well? We do want the ability to have > all the different products installed on our computers. This is the approach I came up with: http://stackoverflow.com/questions/471424/wix-tricks-and-best-practices/578340#578340 It's a hack, no doubt about it, but I've seen no other solution for how to generate unique Guid's if you want to install your product multiple times on the same computer using the same wxs files. cheers si ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
