You should be able to achieve something similar in Votive maybe using pre-processor definitions if you can't simply exclude files from the build.
However I make extensive use of Fragments & ComponentRef, ComponentGroupRef, FeatureRef & FeatureGroupRef's to avoid duplicating any code where ever possible since I have a lot of stuff shared between 2 or more of my installers so I may be looking at this from a different position. If I had to make multiple versions of the same package with slight differences, I'd make a new .wixproj for it, author one .wxs file with the differences & add all the other required Fragments. Akshi you can use preprocessor variables to specify things like ProductCode during a build. See http://wix.sourceforge.net/manual-wix3/preprocessor.htm Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: 20 August 2010 13:50 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Release feature of Installshield in WIX This is something I've been meaning to tackle as I make extensive ( and I mean really extensive ) use of Product Configurations and Release Flags in InsallShield. Basically with WiX you have to break everything out into fragments and then instead of using release flags you use FeatureRef and FeatureGroupRef elements to pull various features into your installer. I think in the end you'll end up having individual wxs files for each product configuration that define the bare minimum variation points such as INSTALLDIR ( INSTALLLOCATION in WiX UI ) , UpgradeCode, ProductCode ( I generate these at build time since I always do major upgrades ). I can basically see it in my mind but I haven't taken the final step yet to actually do it on a large scale and see the pain points. Currently I use WiX to generate close to 1000 merge modules and then use WiX fragements with some custom code to transform them into InstallShield Automation Interface calls. Basically I take a template Basic MSI and build up the feature tree and product configuration at build time using wxs files. My next step will be to create a pure wix version of this; I just don't have it on my roadmap yet. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me ----- Original Message ---- From: akshi_gupta <akshi.gupt...@gmail.com> To: wix-users@lists.sourceforge.net Sent: Fri, August 20, 2010 7:32:44 AM Subject: [WiX-users] Release feature of Installshield in WIX Hi All, I have a couple of questions regarding WIX. How can I have multiple releases(like in Installshield) with one project? Also is it possible to specify any property like PRODUCTCODE during building the project? Thanks, Akshi -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Release-feature-of-Installshield-in-WIX-tp5444328p5444328.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
