How to write Environment Varibles?
Hi guys!
I'm building a package called SoftComex on WPS SP3, this package obviously installs a lot of files, makes some changes in registry and finally it have to write the environment variables.
I've received the following requirement: The environment variable have to contain (C:\Centura;C:\Oracle\Client_10203\BIN). So, I did it on Installation Expert -> "environment variables"; there I wrote two variables, one called Path with the value INSTALLDIR and the other one called Oracle with the value (C:\Oracle\Client_10203\BIN).
But, during installation the environment variables weren't changed. Is there any other way to do the trick?
I'm building a package called SoftComex on WPS SP3, this package obviously installs a lot of files, makes some changes in registry and finally it have to write the environment variables.
I've received the following requirement: The environment variable have to contain (C:\Centura;C:\Oracle\Client_10203\BIN). So, I did it on Installation Expert -> "environment variables"; there I wrote two variables, one called Path with the value INSTALLDIR and the other one called Oracle with the value (C:\Oracle\Client_10203\BIN).
But, during installation the environment variables weren't changed. Is there any other way to do the trick?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
aogilmor
13 years ago
first, make sure INSTALLDIR is the directory you think it is, sometimes wise sets it to a higher level dir
second, if it's a system variable may need to restart.
second, if it's a system variable may need to restart.
Posted by:
anonymous_9363
13 years ago
If it's a system-level variable, it will need a reboot. That's the principal reason why I use user-level variables, as one should strive to remove the requirement to reboot as much as possible.
Of course, this brings up two points: one, why, in 2010, are vendors still pushing out software which uses these variables and two, why doesn't the WI engine provide a mechanism for propagating the change, like the Control Panel applet does? After all, it requires just a single API call.
Of course, this brings up two points: one, why, in 2010, are vendors still pushing out software which uses these variables and two, why doesn't the WI engine provide a mechanism for propagating the change, like the Control Panel applet does? After all, it requires just a single API call.
Posted by:
cmi2000
13 years ago
Thank you! I've chosen "Installation per-machine" and "reboot always" options, now it's working.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.