Click here to Skip to main content
Click here to Skip to main content

Invoke another MSI from an MSI

, 4 Mar 2009 CPOL
Rate this:
Please Sign up or sign in to vote.
Demo showing how to invoke a Microsoft Windows Installer wrapped in a Microsoft Windows Installer.

Introduction

I was looking for a way to solve the problem of Windows’ concurrent (nested) installations as described in the URL: http://msdn.microsoft.com/en-us/library/aa368010(VS.85).aspx. My goal is to wrap an MSI based InstallShield EXE or MSI within the Visual Studio Windows Installer Project. I was able to find some useful tips online, and I have converged the information and found a solution described below. I also found Arnaldo Sandoval's "Installer Class and Custom Actions" article very helpful (URL: http://www.devcity.net/Articles/339/1/article.aspx).

How it works

I created two projects in the solution:

  • InstallerHelper – A console application project with C# code to enable code based custom actions.
  • MsiInstaller – A Windows installer project that creates the MSI.

First, for the InstallerHelper project, I created two simple classes:

  • InstallerClass - This installer class overrides the base installer class to provide additional functionality for Custom Actions.
  • InstallerHelper - This helper class is used to invoke the MSI based InstallShield EXE or MSI.

In general, the InstallerClass class calls the InstallerHelper class to invoke the MSI based InstallShield EXE or MSI. Here is what I have achieved in my MSI installer demo:

MsiDemo

Next, for the MsiInstaller project, I added to the File System both the output from the InstallerHelper project, and the MSI based InstallShield EXE or MSI to be installed on the target machine. I found that you can actually drag and drop multiple dependency files and folders to the File System view.

VS001

I added the primary output InstallerHelper as the Custom Actions for all.

VS002

This achieves the goal of invoking an MSI within a Visual Studio Windows Installer Project. When I run the MSI, it will first install the MSI based InstallShield EXE or MSI, but not executing it. Then, it runs the InstallerHelper which kicks-off the EXE or MSI.

Tips

A tip I found is that if the imported MSI based InstallShield EXE or MSI already contains Custom Actions, which is very common, then when you add the EXE or MSI to the Visual Studio Windows Installer Project, the Custom Actions is carried over to the Windows Installer Project. This gives the undesirable result of concurrent installation because some of the Custom Actions from the embedded MSI are invoked while the wrapper MSI is running. A simple solution is to use Orca.exe, select the CustomAction, and delete the ones that are being imported form the embedded EXE or MSI install process.

History

  • Feb 2009 - first release.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

A. Kwan
Systems Engineer
Canada Canada
No Biography provided

Comments and Discussions

 
QuestionDO NOT USE THIS APPROACH ! PinmemberTarmo Pikaro18-Oct-13 12:30 
QuestionThank You PinmemberIamPhani29-May-13 2:51 
SuggestionIf the main objective is just to call a second *.msi than... Pinmembernetxsk11-Jan-13 4:37 
In the InstallerHelper.cs you can only have the Main method, like this:
using System;
using System.Diagnostics;
using System.IO;
 
//-----------------------------------------------------------------------------

namespace InstallerHelper
{
    static class InstallerHelper
    {
        static void Main(string[] args)
        {
 
        }
    }
}
 
//-----------------------------------------------------------------------------
 
and in the InstallerClass.cs you call:
...
protected override void OnCommitted(IDictionary savedState)
{
    base.OnCommitted(savedState);
 
    Process installerHelperProcess = new Process();
 
    installerHelperProcess.StartInfo.UseShellExecute = <bool>;
    installerHelperProcess.StartInfo.CreateNoWindow  = <bool>;
    installerHelperProcess.StartInfo.WorkingDirectory = <Path to the second msi>;
    installerHelperProcess.StartInfo.FileName         = <msi file name and extension>;
    installerHelperProcess.StartInfo.Arguments        = <arguments for /passive or /quiet and other params>;
 
    installerHelperProcess.StartInfo.WindowStyle = <ProcessWindowStyle>;
 
    installerHelperProcess.Start();
}
...
 
You will continue to your primary.msi while the other is intalling in the background.
GeneralRe: If the main objective is just to call a second *.msi than... PinmemberMember 961819220-Mar-13 3:03 
GeneralRe: If the main objective is just to call a second *.msi than... Pinmembernetxsk26-Apr-13 3:43 
SuggestionYou can also do to the same thing by using Visual Studio Custom Prerequisites Pinmemberkensurferca13-Dec-11 15:07 
GeneralUsing predefined installation path in nested installer Pinmembertonyt2-Dec-09 6:52 
GeneralRe: Using predefined installation path in nested installer Pinmembernetxsk11-Jan-13 4:17 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web02 | 2.8.141216.1 | Last Updated 4 Mar 2009
Article Copyright 2009 by A. Kwan
Everything else Copyright © CodeProject, 1999-2014
Layout: fixed | fluid