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
- :
- Help with evaluating 2008 premium as an upgrade route from IS Developer 8.2
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 24, 2007
10:32 AM
Help with evaluating 2008 premium as an upgrade route from IS Developer 8.2
We have been using InstallShield developer 8SP2 for the past 5 years and have written many scripts using the IS COM Automation API to build releases and patches.
We were considering upgrading to version 12, but 2008 has just become available (not sure of the differences) and so we will now consider 2008.
I've been asked to evaluate the work involved in porting our installs (3 of them) and the scripts which build releases/patches.
I'm downloading IS2008 premium evaluation edition. Does this give me access to the Standaline build so I can test automation API scripts for the 21-day evaluation period?
Also, our projects are all InstallScripts MSI - we wanted a flexible script-driven UI (the windows installer of 2002/03 was terrible for UI development) coupled with an MSI engine deployment so we went for a hybrid model rather than a Basic MSI. Is there any good references which highlight problems with upgrading InstallScript MSI project types?
Many thanks.
-Alastair
We were considering upgrading to version 12, but 2008 has just become available (not sure of the differences) and so we will now consider 2008.
I've been asked to evaluate the work involved in porting our installs (3 of them) and the scripts which build releases/patches.
I'm downloading IS2008 premium evaluation edition. Does this give me access to the Standaline build so I can test automation API scripts for the 21-day evaluation period?
Also, our projects are all InstallScripts MSI - we wanted a flexible script-driven UI (the windows installer of 2002/03 was terrible for UI development) coupled with an MSI engine deployment so we went for a hybrid model rather than a Basic MSI. Is there any good references which highlight problems with upgrading InstallScript MSI project types?
Many thanks.
-Alastair
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 24, 2007
10:57 AM
For considerations to bear in mind when upgrading MSI projects that use InstallScript, please see [thread=169870]this thread[/thread].