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: Setting ProductVersion on an InstallScript project from MSBuild.
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
‎Apr 13, 2011
04:18 PM
Setting ProductVersion on an InstallScript project from MSBuild.
Hi,
I'm trying to set up a Team Foundation Server build that ultimately creates an installer with the appropriate version. I'm having trouble getting InstallShield to recognize the version that I'm passing in. I'm doing something like this:
Everything I'm passing in (path variables, output directory, configuration, etc..) works fine except for ProductVersion. No matter what I put there, my installer just comes out with the version set to the default value from the General Settings page in the .ism itself.
I am using an InstallScript-only project (no MSI support). Does that have anything to do with it? If not, what else should I be looking at?
Thanks,
Nathan
I'm trying to set up a Team Foundation Server build that ultimately creates an installer with the appropriate version. I'm having trouble getting InstallShield to recognize the version that I'm passing in. I'm doing something like this:
PATH_TO_DEBUG_FILES
ReleaseConfiguration="Release"
PathVariables="@(InstallShieldPathVars)"
OutDir="$(BinariesRoot)\Win32"
ProductVersion="3.4.5"
InstallShieldPath="$(InstallShieldPath)" />
Everything I'm passing in (path variables, output directory, configuration, etc..) works fine except for ProductVersion. No matter what I put there, my installer just comes out with the version set to the default value from the General Settings page in the .ism itself.
I am using an InstallScript-only project (no MSI support). Does that have anything to do with it? If not, what else should I be looking at?
Thanks,
Nathan
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 19, 2011
02:24 PM
Bump? I still haven't had any success getting this to work.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 20, 2011
09:26 AM
(Disclaimers first) I've never tried to pass so much stuff on the command line, and I've never worked with TFS.
Back when I was integrating my InstallScript installers with the application builds, I would write a vbscript which used the InstallShield Automation Interface. It's a set of COM objects and methods which allow you to upen an ISM, navigate through the elements of your project, and allows you to set things like the Version, and other things as well. It's an old and honored technique in this community. It's (fairly) well documented on the Flexera website.
I've attached a sample script, which I wrote recently to examine ISMs for compliance with some of an organization's standards. It mostly just looks at stuff, but in some instances it changes things too. It was written quickly, so it's a bit inelegant, but it should be enough to give you a rough idea.
Regards,
Back when I was integrating my InstallScript installers with the application builds, I would write a vbscript which used the InstallShield Automation Interface. It's a set of COM objects and methods which allow you to upen an ISM, navigate through the elements of your project, and allows you to set things like the Version, and other things as well. It's an old and honored technique in this community. It's (fairly) well documented on the Flexera website.
I've attached a sample script, which I wrote recently to examine ISMs for compliance with some of an organization's standards. It mostly just looks at stuff, but in some instances it changes things too. It was written quickly, so it's a bit inelegant, but it should be enough to give you a rough idea.
Regards,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 20, 2011
09:45 AM
Thanks for the tip -- I'll go read up on the automation interface...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 25, 2011
10:58 AM
Update: that worked. I created some custom MSBuild tasks in C# and talked to the Automation Interface through those. Version number is updating fine with that method.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)