Summary

Synopsis

Discussion

InstallShield X and later users

In IntallShield X and later, there is a Component Services view that allows COM+ applications to be set up quite easily.

DevStudio 9.x and earlier users

1. The COM+ application first must be exported into an .msi file format. This is not necessary if your COM+ application is already in an .msi file format.

   Note: For more information about this step, browse to the Administrative Tools section of the Windows NT, Windows 2000, or Windows XP operating system and enter COM Application Export Wizard in the search tab.

2. Open a new or existing .ism file in InstallShield. This step is required because an .msi formatted COM+ application has no user interface.

   Note: COM+ MSI applications are not considered standalone applications and, therefore, require a parent installer.

3. Include the COM+ MSI into a parent installer.
   1. Open the Custom Action Wizard.
   2. In the Action Type panel of the wizard, select the "Launch another .msi package" option in the Type field and set the Location field to "Included with Your main setup" or "Stored on the Source Media."
   3. On the Action Parameters dialog, browse to the MSI. You can also pass public properties in the Target section.
4. Insert the custom action into the sequence.
   1. When sequencing the custom action, make certain that it executes before InstallInitialize and After CostFinalize.
   2. Schedule the custom action to be launched before files that require the COM+ as a dependency.
   3. Include a condition on the custom action of Not Installed when inserting it into the sequence.

Additional Information

For more information on how to accomplish steps 3 and 4, see InstallShield Knowledge Base article : Nested Installation

For more information on custom actions, see InstallShield Help Library topic Using Custom Actions.