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
- :
- How to handle different editions of the same program
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
‎May 09, 2017
08:39 AM
How to handle different editions of the same program
What is considered the best practice for handling different editions of the same program?
IE, a program that has Development, Beta, and Release editions. These editions can all be on a computer at the same time, so they have different folders for data and different registry values so they can coexist peacefully.
How can this be handled in InstallShield?
IE, a program that has Development, Beta, and Release editions. These editions can all be on a computer at the same time, so they have different folders for data and different registry values so they can coexist peacefully.
How can this be handled in InstallShield?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 11, 2017
09:45 AM
Sure InstallShield can handle that - You'd want to make each of them look like totally different programs with nothing in common - different GUIDS for Package, Product and Upgrade codes than each other - different registry keys than each other - different GUIDs throughout the product, etc, etc.
If you think of them as being 3 unrelated products it should be what you are after.
Chad
If you think of them as being 3 unrelated products it should be what you are after.
Chad
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 11, 2017
01:48 PM
Ok, I understand treating them as different programs -- but can all that be handled elegantly within a single .ism file?
Currently each type of build has a different .ism file, which makes maintaining a nightmare since if you make a change to one, you have to change all of them. I'm trying to consolidate each .ism file into a single .ism file and it seems quite hacky to do so.
Currently each type of build has a different .ism file, which makes maintaining a nightmare since if you make a change to one, you have to change all of them. I'm trying to consolidate each .ism file into a single .ism file and it seems quite hacky to do so.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 15, 2017
11:25 AM
No, you wouldn't be able to have 3 different products packaged into one installer - for 3 distinct products you'd need 3 ISM files.
Chad
Chad