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: Path Variable Overrides Broken
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 23, 2014
10:35 AM
Path Variable Overrides Broken
We have upgraded from 2013 to 2014 and now all our projects are building with the wrong files.
The problem appears to be that Path Variable Overrides are not working properly if one path variable refers to another. Here is an example of path variables using an InstallScript project type:
VER_FOLDER = 2013
X86_FILES = C:\Build Files\\x86
X64_FILES = C:\Build Files\\x64
If I set "VER_FOLDER" in the "Path Variable Overrides" section of the media to "2014", it still uses "2013" in the path variables "X86_FILES" and "X64_FILES" when built.
It works fine if I directly override "X86_FILES" or "X64_FILES". However, the above is just an example; we have many more path variables that refer to VER_FOLDER.
This worked fine in earlier versions so how do I resolve this?
The problem appears to be that Path Variable Overrides are not working properly if one path variable refers to another. Here is an example of path variables using an InstallScript project type:
VER_FOLDER = 2013
X86_FILES = C:\Build Files\
X64_FILES = C:\Build Files\
If I set "VER_FOLDER" in the "Path Variable Overrides" section of the media to "2014", it still uses "2013" in the path variables "X86_FILES" and "X64_FILES" when built.
It works fine if I directly override "X86_FILES" or "X64_FILES". However, the above is just an example; we have many more path variables that refer to VER_FOLDER.
This worked fine in earlier versions so how do I resolve this?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 24, 2014
10:42 AM
Work order IOJ-1663112 has been submitted to address this issue.
As a work around can you try using lower case for any path variables that you intend to override. So in the example you give you would want to change VER_FOLDER to ver_folder in all places it is used.
Please let me know if there are any issues with this work around.
As a work around can you try using lower case for any path variables that you intend to override. So in the example you give you would want to change VER_FOLDER to ver_folder in all places it is used.
Please let me know if there are any issues with this work around.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 25, 2014
09:45 AM
JohnCresswell wrote:
Work order IOJ-1663112 has been submitted to address this issue.
As a work around can you try using lower case for any path variables that you intend to override. So in the example you give you would want to change VER_FOLDER to ver_folder in all places it is used.
Please let me know if there are any issues with this work around.
Hi John
I edited the .ISM project file directly and did a search and replace to change my path variable overrides to lowercase (luckily they had more unique names than my example) and it seems to have worked, thank you.
Regards
Michael