I'd like to create a package that contains a number of separate installs.

During the install of the package I'd like the user to be able to select the required applications to install.

I've downloaded a few demo apps from the tools section of this site, but I can't seem to work out how to do it.

Any pointers in the right direction would be appreciated.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hi ,

I have never tried this before but here is a way by which you can achieve this :

1) Create Features for different msi's to install in your base package
2) Create nested installation custom actions (CA's) for all msi's
3) use Install Conditions of different CA's to install only those msi's for whom user has selected the related feature during installation

There may be better ways of achieving this .

Cheers ,
Answered 10/20/2005 by: viv_bhatt1
Senior Purple Belt

Please log in to comment
If you can get a hold of a tablet PC, there's an excellent example of this in the Microsoft Tablet PC Experience pack.

They basicaly have a Launcher.msi that contains nested MSI's in the form of DAT files. Launcher.msi drops an icon in start that brings up a a GUI that displays information on each of the 7 applications contained in the install, and then gives the user the option to install them.

It was created with Installshield, but beyond that I don't know much about the install. I needed a package of just 1 of the 7 contained apps, and ended up repackaging it. If I'd had more time, I was able to extract the individual MSI's from the .dat files, and I could have eventually figured out how to rip out the custom action that required it be installed from the launcher, but time is a luxury I don't have right now.
Answered 10/20/2005 by: Bladerun
Green Belt

Please log in to comment
That's interesting - nice one Bladerun.

I checked it out - basically it writes all the .dat files to C:\Documents and Setting\All Users\Application Data\Microsoft\Experience Pack\Data (you can rename them all to .msi apart from SnipTool which has to be renamed to an .exe)

These installs are kicked off by C:\Program Files\Micrsoft Experience Pack\ExpPack.exe so u'd have a job customising the whole thing to suit your own apps but at least you can get to the vendor MSI's for the MS apps - maybe useful one day...


P.S. You can hack the launch conditions on InkArt.msi so it installs on a normal desktop - quite a nice little app, especially if you have a graphics tablet. You can do the same with the EnergyB.msi (desktop theme) the other apps will only run on Tablet OS though - shame as I was keen on doing a crossword at lunchtime!
Answered 10/24/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment

I have a similar problem. I'm using Installer2go to create a setup file where the user has the choice of 3 different SW versions to install. How can I do this. I created 3 nested msi files within the deplyment file and tried to call them with a vbscript, but I have no clue how to call them conditionally. What does "Property Value" mean in this case? How has the script to look like? Or are there better ways to implement this?

I have pretty few knowledge in this subject and I'm thankful for every hint/help you can give me!

Answered 10/26/2005 by: chubbachubb
Yellow Belt

Please log in to comment