Hello,
We're evaluating using Advanced Installer to replace an ad-hoc install/update methodology we've been using for a desktop product.
It seems that getting a fresh install up and running, with all our special folder requirements et al is quite simple, and using the patch tool to diff between two MSIs works wonderfully. The questions I'm running into are based on efficiency and methodology.
Our product has many separate pieces, some of which do not require a recompile of the main binaries (things like XML config files, external data files, etc). With our current ad-hoc solution, I can push out updates for just this one portion of our app. I'm struggling to find the *best* way to do this using Windows Installer/Advanced Installer. Here's the rub - we don't want the users to be able to de-select items. we want to require them to update all-or-none. I could still see this working with the patch created from two different MSIs, but since we're not rebuilding the main binary the product version would it be necessary to rebuild to simply increment the version number? (assuming I base the product version on the main binary build version).
I'm a little unclear on making patches - from the looks of things, I have to build a base MSI, and every update is a patch off of that - otherwise a user who skips a version in their updates would have to download patch 1, install it, then download patch 2 and install that - if I'm mistaken please advise.
Tying into the previous question - I'd also like to know if there is any best practice when it comes to a slightly different situation, such as 3rd party components that must be linked into the main app, but do not change as frequently as the main app. For instance - a vendor supplied UI component, might stay unchanged for a year, while our app is patched 3 times. Is it best to just include the vendor component(s) in the main MSI (where they'll contine to be distributed in patch after patch) or would that be better served as a prerequisite, hosted in a separate installer (which is only an option for us if we can force the user to take that update along with the update to our binaries).
I know that's a lot of questions to drop, sorry for so many, but we're excited to find an app like this that can help us move to a more stable install/update solution than what we're currently using - thanks for your help.
FOLLOW US
Get the latest news in Application Packaging