We need to install a chained MSI with our product but I'm not quite sure what to do with it. I've seen the chained MSI screen but we need to install this MSI based on a feature selection and not already installed. What is the syntax for that? Also, how do I ensure that the MSI is not removed when our software is uninstalled?
Does the &FeatureName syntax described in "Conditional Statement Syntax" work?
If you haven't yet, you might consider also looking at the white paper on the topic, mentioned in this thread at the top of the forum: [thread]185662[/thread].
I tried to download the whitepaper. After I got through the registration I got a link to the PDF file but the redirection no longer works. I was not able to collect the whitepaper.
So honolua have you got chaining to do what you wanted?
We are looking at Chaining a bunch of our install projects together to make a kind of suite install but need to know if it can handle Web downloads where it will only download and install the user selected features as well as if it can handle patching/Minor upgrades as well?
Have you experience in any of these methods? How about admin installs - does the admin have a single msi to push or do they still have to push the individual msi projects?
