Set Enviornment Variable issue
Posted: Wed Nov 30, 2011 9:54 am
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.
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.