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
- :
- Re: Major Upgrades - How to automatically update the product code?
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
‎Sep 02, 2009
03:03 PM
Major Upgrades - How to automatically update the product code?
Not exactly sure if this is the correct way to do this, but this is how we are doing it currently.
We want a Major upgrade every release and to for the install to uninstall all of the product and put the new product into place. To get that result we change the version number and product code but leave the upgrade code the same.
Currently we are manually changing the product code each release before we start our automated builds. Is there a way (by command line?) to generate a new Guid or pass in a new Guid? We currently pass in the product version with -y
We want a Major upgrade every release and to for the install to uninstall all of the product and put the new product into place. To get that result we change the version number and product code but leave the upgrade code the same.
Currently we are manually changing the product code each release before we start our automated builds. Is there a way (by command line?) to generate a new Guid or pass in a new Guid? We currently pass in the product version with -y
(6) Replies
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 03, 2009
12:08 AM
I used VBScript to do this. First I changed the ISM file format to XML , so that I can easliy use DOM objects to do all required actions.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 04, 2009
04:43 AM
You can do this via the IS Automation Interface.
1. Create an IswiAuto15.ISWiProject/SAAuto15.ISWiProject object (take IS2009 for example).
2. Call the GenerateGUID method to generate a new GUID.
3. Pass the value to ProductCode property.
1. Create an IswiAuto15.ISWiProject/SAAuto15.ISWiProject object (take IS2009 for example).
2. Call the GenerateGUID method to generate a new GUID.
3. Pass the value to ProductCode property.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 14, 2009
03:17 PM
1) How do I convert my ISM to XML? I have been looking all over for this.
2) Automation Interface?
2) Automation Interface?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 14, 2009
04:05 PM
General Info > Project Properties > Project File Format is where you choose between Binary (MSI) and XML formats. The project file ends with the .ism extension, regardless of format, and the InstallShield Automation interface works with the project file in either case.
Please see the help topic References > Automation Interface for more information about that.
Please see the help topic References > Automation Interface for more information about that.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 14, 2009
04:19 PM
I just found the converting to XML part right before you posted.
The Automation Interface thing I am still a little confused on. this is a dll that you can interface with and I can use it in my build process by calling functions in the dll with scripts? Does this support C#?
The Automation Interface thing I am still a little confused on. this is a dll that you can interface with and I can use it in my build process by calling functions in the dll with scripts? Does this support C#?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 14, 2009
07:40 PM
Right, the Automation interface is for manipulating a project from outside the InstallShield environment. The examples are set up to use VBScript, but you can use C/C++, Perl, .NET languages, etc., with a bit of translation. Searching these forums and the KB will turn up examples.