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: Accessing ProductVersion Property in Launch .EXE Custom Action
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, 2009
10:46 PM
Accessing ProductVersion Property in Launch .EXE Custom Action
I need to update a database table with the ProductVersion of the InstallShield package. I have created a simple application that updates the database table using a command line input parameter. However, I can't seem to supply the ProductVersion property value to the .EXE through the command line call.
Is it possible to refer to the ProductVersion property from a custom action when launching an .EXE? If so, what is the syntax? I have tried to use the [ProductVersion] syntax, but the value provided to the .EXE is empty.
Thanks in advance,
Dan
Is it possible to refer to the ProductVersion property from a custom action when launching an .EXE? If so, what is the syntax? I have tried to use the [ProductVersion] syntax, but the value provided to the .EXE is empty.
Thanks in advance,
Dan
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 14, 2009
09:38 AM
Using [ProductVersion] as a command-line argument should work. As a test, does your EXE work if you pass in a different property, or a hard-coded version?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 15, 2009
03:43 PM
Robert,
First, thank you for the quick reply.
Second, you were right. It turns out that the command line application didn't like the dot notation of the version number. It required me to put quotes around the [ProductVersion] property reference. Once I did that, everything worked as expected.
Thanks,
Dan
First, thank you for the quick reply.
Second, you were right. It turns out that the command line application didn't like the dot notation of the version number. It required me to put quotes around the [ProductVersion] property reference. Once I did that, everything worked as expected.
Thanks,
Dan