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
- :
- Re: Questions about multiple release configurations
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
Nov 18, 2010
10:24 AM
Questions about multiple release configurations
I am attempting to author an InstallScript installer that has 2 Release configurations. Configuration A contains Feature A, and Configuration B contains Features A and B. Basically, the B configuration includes a Security component that costs extra.
- Is it possible at runtime, to determine which release configuration is being run?
- Is it possible to assign different splash screens and displayed product names, etc. based on the Release configuration, (at design time would be fine for this one)?
Or am I better off authoring a 2nd installer?
Thanks
- Is it possible at runtime, to determine which release configuration is being run?
- Is it possible to assign different splash screens and displayed product names, etc. based on the Release configuration, (at design time would be fine for this one)?
Or am I better off authoring a 2nd installer?
Thanks
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 18, 2010
10:37 AM
lonewolf32 wrote:
I am attempting to author an InstallScript installer that has 2 Release configurations. Configuration A contains Feature A, and Configuration B contains Features A and B. Basically, the B configuration includes a Security component that costs extra.
- Is it possible at runtime, to determine which release configuration is being run?
- Is it possible to assign different splash screens and displayed product names, etc. based on the Release configuration, (at design time would be fine for this one)?
Or am I better off authoring a 2nd installer?
I've developed a project with two releases, similar to the two you've described. I distinguish them at runtime by a Property...when it's set to 0 it's Release A, when it's 1 it's Release B.
When I build each Release, I update the Property through automation (example: http://community.flexerasoftware.com/showthread.php?p=462204#post462204). Then, throughout my project, I run particular tasks based on the Property's value.