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 do you organize installs and upgrades?
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
Oct 29, 2008
09:35 AM
How do you organize installs and upgrades?
InstallShield MSI
I have read all the detailed documentation on major, minor, etc. upgrade types but I’m not sure how to use InstallShield UI correctly. I’m sure this is stupidly simple but I just can’t get a handle on it.
After creating the initial install .ism do I create a new .ism file and add the next upgrade elements or do I keep adding to the same .ism? If you do use the same .ism when is the best time to use a new .ism?
Thanks
I have read all the detailed documentation on major, minor, etc. upgrade types but I’m not sure how to use InstallShield UI correctly. I’m sure this is stupidly simple but I just can’t get a handle on it.
After creating the initial install .ism do I create a new .ism file and add the next upgrade elements or do I keep adding to the same .ism? If you do use the same .ism when is the best time to use a new .ism?
Thanks
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 30, 2008
10:58 AM
No responses. Does anyone understand what I'm asking or is it a hard question? :confused:
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 30, 2008
04:32 PM
As long as you use version control and can always get back to your previous files, there's no big problem in using the same ISM file and just updating. Although I do fork and technically work on a copy between major releases. I only recreate ISM files if i'm moving to a drastically different setup architecture and would like to start fresh.
As an example today I created a new install that is a major upgrade of my previous software (well actually it's a major upgrade to about 4 previous versions of my software), all i did is open my ISM file and create new guids for Package Code, Product Code, and change the Product Version. (FYI, if it were minor upgrade I would just do the Package Code and Product Version).
As an example today I created a new install that is a major upgrade of my previous software (well actually it's a major upgrade to about 4 previous versions of my software), all i did is open my ISM file and create new guids for Package Code, Product Code, and change the Product Version. (FYI, if it were minor upgrade I would just do the Package Code and Product Version).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 30, 2008
05:23 PM
Schmoli thanks for the Help! 🙂