Call DLL and Set Variable order execution
Posted: Wed Nov 07, 2007 8:26 pm
In evaluating InstallAware for our product, we encountered an issue where we cannot sequence the order of execution of a CALL DLL which extracts an encrypted password that is then displayed in a dialog, and the SET VARIABLE required to use that variable.
The CALL DLL executes first, and the SET VARIABLE executes second, no matter what the sequence is in the script. The value of the SET VARIABLE is always populated in the dialog, not the value extracted from the CALL DLL. This is a major setback in our evaluation because we require the extraction of an encrypted password, then to display it in a dialog to give the user a chance to reinstall without compromising the storage of the password in non-encrypted form.
It seems the SET VARIABLE is always executed on a different thread after a CALL DLL thread is running (pre-install), thus destroying the verified result of the CALL DLL used to return the string by reference. Any idea how to sequence these two commands?
The CALL DLL executes first, and the SET VARIABLE executes second, no matter what the sequence is in the script. The value of the SET VARIABLE is always populated in the dialog, not the value extracted from the CALL DLL. This is a major setback in our evaluation because we require the extraction of an encrypted password, then to display it in a dialog to give the user a chance to reinstall without compromising the storage of the password in non-encrypted form.
It seems the SET VARIABLE is always executed on a different thread after a CALL DLL thread is running (pre-install), thus destroying the verified result of the CALL DLL used to return the string by reference. Any idea how to sequence these two commands?