Community Forums
Results 1 to 4 of 4

Thread: How to handle different editions of the same program

  1. #1
    Join Date
    Apr 2017
    Posts
    11

    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?

  2. #2
    chad.petersen Guest
    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

  3. #3
    Join Date
    Apr 2017
    Posts
    11
    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.

  4. #4
    chad.petersen Guest
    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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •