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
- :
- Environment variables set is not visible within the session of installation
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 15, 2008
04:31 PM
Environment variables set is not visible within the session of installation
I created a install script project. The dependent DLL files were copied to a folder under common files folder instead of the system folder. During the installation, the path environment were set to point to this custom folder. When the installation is done, in the AfterFirstUIAfter event, a pop up window will ask the user to choose whether to run the application. If the user choose yes, the application fails because the dll files cannot be found. However, if the user run the application from outside the installer, everything is fine. Or, after quit the installation, the application works fine too. (No restart required).
It looks to me the installshield will not use the new environment variable during the installation process. Is there anyone has a solution for that? Thanks very much for your help.
It looks to me the installshield will not use the new environment variable during the installation process. Is there anyone has a solution for that? Thanks very much for your help.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 15, 2008
04:57 PM
I know in MSI a custom action won't see the new environment because the service control manager that hosts msiexec doesn't refresh enviornment changes. I'm not sure about InstallScript.
Generally when I have this type of problem I modify the environment for the running process.
http://www.microsoft.com/technet/scriptcenter/guide/sas_wsh_kmmj.mspx?mfr=true
Instantiating a Shell Object from within InstallScript and then setting a process environment variable should make it available for whatever comes next in InstallScript.
Generally when I have this type of problem I modify the environment for the running process.
http://www.microsoft.com/technet/scriptcenter/guide/sas_wsh_kmmj.mspx?mfr=true
Instantiating a Shell Object from within InstallScript and then setting a process environment variable should make it available for whatever comes next in InstallScript.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 15, 2008
06:58 PM
Thank you, Christopher. I will try that.