I was wondering what is the best way to tackle this scenario, if at all
but I know that it does get done, ex: ms office
I would like to be able to create an msi whose features are other msi's
but any feature in the parent msi would some how have to be the features of the child msi
I did some reading in the forums and it doesnt look promising
or it seems that type of msi has some big negatives
Also, I am wondering how ms office or other software packages are doing it
I guess I'm going to have to try and disect an ms office cd to see what they have done
It would be really nice if I could add a feature in an msi and point it to another msi
and have all the options of that msi get auto created in that feature
to also include for user changes, for ex: install dir etc.
