The best way to do this is to ask yourself (or whoever made the decision) whether you really need multiple versions for customers. In most situations you should be able to get away with just one installer and if you really need to, allow some parts of it to be optional to the end user.
If this is impossible or out of your control you could make you installation modular with a core product MSI and a documentation MSI(s) and make separate burn bundles for customers. If you do this then most of your patches will be to the core MSI and can be applied to all the products you release regardless of customer and you may choose to patch any doc MSIs separately. Dave -----Original Message----- From: Sanjay Poria [mailto:sanjay.po...@xanalys.com] Sent: 25 January 2012 15:46 To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] MSI setup for different flavours of Product I'm hoping for some advice about MSI and Patching using Wix. I am currently moving one of products from Installshield to MSI using Wix to generate it. Our product has a number of different variations depending on which customer we deliver to. Typically all the different versions differ in a few documentation files (we give some customers more documentation about the back end system than others). The way we achieved this previously with installshield was to have a folder on disk that sits alongside the product installer. At the end of any installation the documentation files in the folder would be copied to the users machine into the install location (implemented using the Installshield scripting language). Previously, we never did any 'real' (in the MSI sense) patching of our products. Once we move to MSI, we would like to produce proper patches (small updates mainly). My question, what is the best way for us (in the MSI world) to produce the variations of our product, so that we can patch easily. What I am hoping for is a solution that is simpler than producing a different product MSI release for effectively, each variant of the product because then I would need to produce multiple patches when the product is basically the same in each case (except for a few doc files). Any help is appreciated. sanjay ----------------------------------------------------------------------------- - Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ 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. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
