How to install a third-party MSI based on Feature - 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!

jfuhr
Posts: 41
Joined: Wed Mar 19, 2008 4:52 pm

How to install a third-party MSI based on Feature

I'm having difficulties launching a third-party's MSI in conjuction with a feature.

This is Microsoft's Office Interop MSI that is needed to integrate our app with Office. However, if you attempt to launch this MSI without Office installed, it will error out.

Because of this, I've created a feature in the standard fashion and created a dialog with a checkbox that allows the user to opt-in for Office installation.

I tried using the Chained Package and a Custom Action (MSI Database Relative to Package). In both, I set the condition to "&OutlookFeature = 3".

The VBS script is running and the feature state is being set, but the MSI never launches.

What am I doing wrong or is there a better way to handle this? The documentation says that you should use Software Pre-req (not an option because you can't condition on feature) or Merge Modules.
jfuhr
Posts: 41
Joined: Wed Mar 19, 2008 4:52 pm

Re: How to install a third-party MSI based on Feature

I was able to resolve this using a Custom attached action and adding it to the Install node.
Frode
Posts: 34
Joined: Thu Feb 26, 2009 3:11 pm

Re: How to install a third-party MSI based on Feature

I am trying to do something like this with .NET 3.5, SQL server etc.

But during install I get the message "The Window Installer service is unavailable. Another application may be running setup. Finish any installation in progress, or restart your computer, and then re-run setup."

I can't run an MSI from another MSI?

Any solutiong/suggestion to this problem?

-frode
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: How to install a third-party MSI based on Feature

Hi,
I am trying to do something like this with .NET 3.5, SQL server etc.
Please note that Advanced Installer has .NET 3.5 and SQL Server as predefined prerequisites, in the Prerequisites page, under the Software Prerequisites tab.

For the moment there is no support for installing other packages based on the selected features, it will be available in a future version. Until then you can create a custom action under InstallFinalize which will launch the EXE packages,one by one, and wait for them to install. There is no predefined custom action to launch an EXE package, but you could use a custom code into that custom action that can launch the package and wait after it.

In the custom action Condition field you can use the Feature Actions. This way you will condition the custom action to run only if the corespondent features have been selected.
I can't run an MSI from another MSI?
You can run a MSI from another one using either the above option or Chained Packages. In this case Chained Packages will not work because you have EXE packages that contain MSI files.

Unfortunately Windows Installer does not support two MSI packages to run at the same time.

Regards,
Bogdan
Last edited by Bogdan on Thu Aug 20, 2009 2:41 pm, edited 1 time in total.
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Frode
Posts: 34
Joined: Thu Feb 26, 2009 3:11 pm

Re: How to install a third-party MSI based on Feature

Hi,

I tried that (InstallFinalize) and used the launch file/url action, but I get the same error.

-frode
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: How to install a third-party MSI based on Feature

Hi,

As I said above Advanced Installer has no predefined custom action for running an EXE package. "Launch File or Open URL" is a predefined custom action.

However, you could use for example a .BAT file that runs your EXE package and waits for its installation to finish. Launch the .BAT file using a "Launch File or Open URL" custom action and set its Execution Properties to “Asynchronous execution, wait for return code at the end of the sequence” radio button.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”