This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Maintaining multiple versions of a product release
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 23, 2008
12:12 PM
Maintaining multiple versions of a product release
I've got a requirement to develop 2 versions of the installer for our product. They are 95% identical except that the "server" version of our product will only be permitted to install on Server 2003/2008 and the "workstation" version will only install on XP/Vista. The "workstation" version will install SQL Express via a setup prerequisite but the "server" version will not install SQL Express.
My question is, is it possible to build both versions from 1 ISM project file? The obvious place I looked at was what sort of variations are possible with multiple IS project "configurations" and "releases". However, these seem more geared to varying how the install is physically packaged and not about varying internal things like OS and prerequisite checks. The only other option I thought of was if the ISM file XML markup differences between the 2 are not too extreme, was to manage an XML transform in our build script to dynamically generate the alternate ISM file at build time. I already use an XML transform at build time to insert the build# at various places. Sounds extreme I know, but I'll do about anything to avoid the maintenance cost of supporting 2 separate ISM project files!
My question is, is it possible to build both versions from 1 ISM project file? The obvious place I looked at was what sort of variations are possible with multiple IS project "configurations" and "releases". However, these seem more geared to varying how the install is physically packaged and not about varying internal things like OS and prerequisite checks. The only other option I thought of was if the ISM file XML markup differences between the 2 are not too extreme, was to manage an XML transform in our build script to dynamically generate the alternate ISM file at build time. I already use an XML transform at build time to insert the build# at various places. Sounds extreme I know, but I'll do about anything to avoid the maintenance cost of supporting 2 separate ISM project files!
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 23, 2008
04:10 PM
Sorry, I should've done some more thorough searches of the forum before posting. This thread had some helpful discussion regarding the use of release flags which was new to me. This does seem to satisfy my immediate needs. However, I would agreed with the suggestions made on that thread getting more control over prerequisite execution in response to user input would be very useful.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 24, 2008
08:11 AM
InstallShield 2009 lets you associate prerequisites with one or more features. A feature prerequisite gets installed if a feature that contains the prerequisite is installed and if the prerequisite is not already installed on the system. You may want to take a look at this new functionality and see if it would meet your requirements.
Here are links to a few InstallShield 2009 help topics that explain more details:
The Read Me First sticky at the top of the InstallShield 2009 Community forum has links to release notes and other documentation that explains what's new in InstallShield 2009.
Debbie Landers
Acresso Software
Here are links to a few InstallShield 2009 help topics that explain more details:
- Associating an InstallShield Prerequisite with a Feature in a Basic MSI or Web Project
- Setup Prerequisites vs. Feature Prerequisites
- Run-Time Behavior for an Installation that Includes InstallShield Prerequisites
The Read Me First sticky at the top of the InstallShield 2009 Community forum has links to release notes and other documentation that explains what's new in InstallShield 2009.
Debbie Landers
Acresso Software