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
- :
- Is there a way to use Path Variables in InstallScript?
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
‎Mar 11, 2011
04:11 AM
Is there a way to use Path Variables in InstallScript?
Hello,
is there a way to use path variables in the script? I can't seem to find the right page in the documentation 😕
Thank you,
ChristianS
is there a way to use path variables in the script? I can't seem to find the right page in the documentation 😕
Thank you,
ChristianS
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 11, 2011
09:15 AM
Hi Christian,
not really sure what you're looking for, but you can access _the_ path variable (containing the ; separated list of folders) via RegDbGetKeyValueEx and the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment / value: Path.
As far as I know, changes take effect after the next reboot.
HTH,
Johannes
not really sure what you're looking for, but you can access _the_ path variable (containing the ; separated list of folders) via RegDbGetKeyValueEx and the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment / value: Path.
As far as I know, changes take effect after the next reboot.
HTH,
Johannes
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 14, 2011
02:09 AM
Hello,
Sorry, I should have expressed myself more clearly.
I meant the Standard path variables you define in the Path Variables View of the InstallShield IDE.
More info:
I use the variables during development to point to the media I want to install. I I want to use the path variables during installation to perform specific actions depending on where the media came from.
Right now I have to change the path variable itself and then copy it by hand into installscript. It would be more convenient if I only had to change it in one place.
Sorry, I should have expressed myself more clearly.
I meant the Standard path variables you define in the Path Variables View of the InstallShield IDE.
More info:
I use the variables during development to point to the media I want to install. I I want to use the path variables during installation to perform specific actions depending on where the media came from.
Right now I have to change the path variable itself and then copy it by hand into installscript. It would be more convenient if I only had to change it in one place.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 15, 2011
03:45 AM
Hello Christian,
the path variables are resolved and "gone" as soon as the install package is built.
Moreover, they do not refer to the installation medium (CD or network or whatever), but to the very source on your developer's machine. I do not think that this file structure is useful information for the installation process running on the user's machine.
If you do want the setup to behave differently depending on the source paths you have built from, you should:
1) Reconsider your design.
2) include this information in a location (separate file, ini entry, ...) that is accessible at installation time.
Best regards, Matthias
the path variables are resolved and "gone" as soon as the install package is built.
Moreover, they do not refer to the installation medium (CD or network or whatever), but to the very source on your developer's machine. I do not think that this file structure is useful information for the installation process running on the user's machine.
If you do want the setup to behave differently depending on the source paths you have built from, you should:
1) Reconsider your design.
2) include this information in a location (separate file, ini entry, ...) that is accessible at installation time.
Best regards, Matthias
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 23, 2011
10:05 AM
Thank you for your answers!
I will consider a redesign although it would have been a neat shortcut...
I will consider a redesign although it would have been a neat shortcut...
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)