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: Using a path variable as a destination folder
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
May 20, 2014
08:23 AM
Using a path variable as a destination folder
Hi,
I'd like to have a destination folder (not my INSTALLDIR), which is defined as a path variable (taken from the registry or the environment variables).
Any ideas? (For Basic MSI project. Non-InstallScript solutions preffered)
Thanks!
I'd like to have a destination folder (not my INSTALLDIR), which is defined as a path variable (taken from the registry or the environment variables).
Any ideas? (For Basic MSI project. Non-InstallScript solutions preffered)
Thanks!
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 21, 2014
02:34 PM
Can you do a system search for the registry entry and set a property name?
If the property name exists then use a set directory custom action to set directory to the value of the property.
Some things to consider if you are setting components to this directory value, what happens to those components if the registry path does not exist? You could place a condition for install on the component to based on the system search property.
I am not certain how to do this if you are looking to use an environment variable rather than a registry entry. I know the InstallShield UI does not make a provision for using environment variables for system searches.
If the property name exists then use a set directory custom action to set directory to the value of the property.
Some things to consider if you are setting components to this directory value, what happens to those components if the registry path does not exist? You could place a condition for install on the component to based on the system search property.
I am not certain how to do this if you are looking to use an environment variable rather than a registry entry. I know the InstallShield UI does not make a provision for using environment variables for system searches.