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
- :
- string vs path variable
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
Jul 25, 2011
02:19 AM
string vs path variable
Hi
In the InstallShield IDE, there is a tip for the "Product Name":
"Instead of hard-coding a value, you can use a path variable. At build time, InstallShield replace the path variable with the appropriate value."
My question is: isn't a public string more appropriate than a path variable? after all product name is a string not a path?! right.
In the InstallShield IDE, there is a tip for the "Product Name":
"Instead of hard-coding a value, you can use a path variable. At build time, InstallShield replace the path variable with the appropriate value."
My question is: isn't a public string more appropriate than a path variable? after all product name is a string not a path?! right.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 25, 2011
02:09 PM
I found out that ISCmdBld (command for building from command line) can be given a path variable, in the command line.
so I guess if one sets the product name as a path variable, one can set different values for the product during build....
Is there a more common way to do that?
so I guess if one sets the product name as a path variable, one can set different values for the product during build....
Is there a more common way to do that?