We've just upgraded to Advanced Installer 3.4 and are now seeing some strange behaviour. When launching our application at the end of the installation from the "Installation Complete" dialog, our application runs from C:\WINDOWS\system32 instead of APPDIR.
We were attempting to find a way to successfully install when a client has an encrypted %TMP% directory. However, we have decided not to find a workaround after all. If a client has an encrypted %TMP% directory they should already know how to work around it.
Can I temporarily set an environment variable (%TMP% in particular) during the install process and set it back to its original value once the install is complete?
Is there any way to detect whether a given folder is encrypted or not using Advanced Installer? I would like to avoid using a Custom Action if at all possible. Maybe something in the new launch condition support in 3.4?
FOLLOW US
Get the latest news in Application Packaging