I am exploring moving a moderate size installer to WiX and I am stumbling through with some good successes thanks to the active support community out there. My application has a large amount (~1gb) of reference data that does not change much from version to version. This data is not required for all installations, but in the past we have installed it by default through a custom action that expands archives to the correct location on the destination machine. Moving forward I would like to put this reference information into a MSI, but I am not sure if it makes sense to use a separate MSI and chain it using Burn or create a Feature and package it in my application's MSI. We release a minor upgrade to our application (not reference data) about quarterly, with a major upgrade yearly. However our reference data will typically only have 5% files replaced and even less added/removed in a given year.
So, is it better to create a separate MSI for the reference data and chain or to include it in the main MSI? What is the best practice here? Thanks for taking the time as I get my WiX feet wet! ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
