cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Pilgrim

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?
Labels (1)
0 Kudos
3 Replies
Highlighted
Occasional contributor

Re: How to handle different editions of the same program

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
0 Kudos
Highlighted
Pilgrim

Re: How to handle different editions of the same program

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.
0 Kudos
Highlighted
Occasional contributor

Re: How to handle different editions of the same program

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
0 Kudos