Installing other MSIs as products in a new MSI - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

slough
Posts: 6
Joined: Wed Aug 01, 2007 3:36 pm

Installing other MSIs as products in a new MSI

Is there a way that I can install other MSI packages as products in a new MSI? For instance, I have already created an MSI for a client application and I want to have this install as an option under the custom installation dialogue for the server application MSI. Ideally there would be a way to spawn other MSI packages based on selected options under the custom installtion.

Thanks,
Steve
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Re: Installing other MSIs as products in a new MSI

Hi,

If you want to keep that MSI as individual installation then you have two options:

1. Use prerequisites. You can read more about prerequisites and how to use them in AI here:
http://www.advancedinstaller.com/user-g ... tware.html

2. Add the MSI as a custom action (and control its execution with a check box in UI), but this is not very recommended because the CA can be scheduled only under "InstallFinalize" standard action with "Asynchronous Execution, do not wait for return code" as "Execution Option" (this is because two MSI package can not be run at the same time).

Other approach would be to use the "MSI Import" feature (using this you create a new package by importing the resources from the existing MSI):
http://www.advancedinstaller.com/user-g ... t-msi.html

Best Regards,
Gigi
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com/
slough
Posts: 6
Joined: Wed Aug 01, 2007 3:36 pm

Re: Installing other MSIs as products in a new MSI

I don't know that I asked the correct question. If I use the Organization feature to add multiple products to an MSI, Is there a way to specify a different default path for each of them or can I only use the default APPDIR from the project? For instance, I want the main application to default to a directory on the data drive and the web reports to default under c:\inetpub\wwwroot. I would also like to specify other paths for use with a client side application, etc. I assume I can not launch another MSI from within the main package, is this correct?

Thanks,
Steve
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Installing other MSIs as products in a new MSI

Hi,
Is there a way to specify a different default path for each of them
We have a Browse for folder how-to which explains how to do this.
I assume I can not launch another MSI from within the main package, is this correct?
Yes, you cannot launch another MSI package while your main installation package is running. This is because Windows Installer doesn't support running two MSI-based installations at the same time.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Olexa
Posts: 17
Joined: Wed Jun 04, 2008 11:34 am

Re: Installing other MSIs as products in a new MSI

gigi wrote:2. Add the MSI as a custom action (and control its execution with a check box in UI), but this is not very recommended because the CA can be scheduled only under "InstallFinalize" standard action with "Asynchronous Execution, do not wait for return code" as "Execution Option" (this is because two MSI package can not be run at the same time).
Advanced Installer 6.3.1 Enterprise does not allow to make MSI Attached Cutsom Action at InstallFinalize to be executed asynchronously. "Asynchronous execution, wait for return code at the end of sequence" and "Asynchronous execution, do not wait for return" options are greyed out.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Installing other MSIs as products in a new MSI

Hi,

This is because the MSI package should not be added as an Attached custom action. Note that when you try to create a "New Attached Custom Action", the "Select a file to execute as a custom action" dialog will show only the supported files (MSI is not one of them). If you need to launch a MSI package at the end of the installation, you can use a "Launch file or open URL" custom action.

A good approach is to use the second MSI as a prerequisite for the main package. This way, the MSI will be installed if it is not found on the target machine. Note that we have a prerequisite tutorial which may help you.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”