Page 1 of 1

Set Enviornment Variable issue

Posted: Wed Nov 30, 2011 9:54 am
by ckaware
If during install (in Native Engine mode) you have something like:
Set Environment Variable %TEST_HOME% to $TARGETDIR$
Apply Install (get result into variable SUCCESS)
and the user doesn't reboot which is required for TEST_HOME to take effect (by IA default)
Then the user for some reason runs the uninstaller, the uninstaller says that it can't remove TEST_HOME= as it doesn't exist (throws an error)
What if instead of a check box on SET ENV to "remove on uninstall" there was a separate DELETE ENV. action?

In the current implementation there's no way to take control of the "remove on uninstall" functionality in the IF REMOVE=TRUE area.

Re: Set Enviornment Variable issue

Posted: Wed Nov 30, 2011 1:50 pm
by giaviv
Hi,

Thank you for your comment. We will look into this.

Re: Set Enviornment Variable issue

Posted: Wed Dec 07, 2011 1:15 pm
by ckaware
I will attach one shortly.

Thanks,

Chris

Re: Set Enviornment Variable issue

Posted: Fri Dec 09, 2011 7:37 am
by ckaware
My firewall is throwing strange errors when I'm trying to upload, not sure what's going on, but to reproduce the issue, place the SET ENV VAR in NATIVE MODE = TRUE to duplicate the issue and have remove on uninstall checked. If the user goes to uninstall prior to rebooting (since set env. doesn't update the system enviornment), we're seeing the issue.