Home/ Questions/Q 6784237
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T16:57:57+00:00

In our company we regularly create MSI’s with Installshield(latest). These setups adhere to a

  • 0

In our company we regularly create MSI’s with Installshield(latest).
These setups adhere to a set of rules and name schemes so they work with our deployment system and autobuilds etc.

Is there a way to eliminate the repetitive overhead of going through all the boilerplate stuff (setting the company meta data, basic folder structures, a few events, including some default helper files etc) for each setup?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Take a look at the InstallShield Automation interface. What I did was:

    1. Abstract all my components out into WiX Merge Modules ( could be IS merge modules though ).
    2. Create a base InstallShield project ( Common.ISM )
    3. Create XML files to describe my feature tree and product configurations
    4. Create Build Automation to reflect the XML and invoke the Automation Interface to “Emit” my installer source.
    5. Build the Product Config in the ISM.

    This gave me a great deal of code reuse but it’s not trivial to set up this type of system. However it scales very well and the advantages are huge if you have the right business needs.

    • 0