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?
preguntado el 08 de noviembre de 11 a las 12:11
Take a look at the InstallShield Automation interface. What I did was:
- Abstract all my components out into WiX Merge Modules ( could be IS merge modules though ).
- Create a base InstallShield project ( Common.ISM )
- Create XML files to describe my feature tree and product configurations
- Create Build Automation to reflect the XML and invoke the Automation Interface to "Emit" my installer source.
- 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.
Hay dos maneras de hacer esto:
- Save the ism file in xml format (there is a setting for this in the project settings). Then in run time, push the desired values with a new application that could be written (which will edit the XML file using DOM or so...)
- Use InstallShield Automation interface. This can be done using VBScript. You may check this link: InstallShield Automation Interface