I confirm this problem.
I am able to get the script to run the preconditions but won't continue on with the rest of the process.
I would really appreciate this being fixed asap as I am in the process of creating an automated build process.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Example script
Logged In: YES
user_id=2035455
Originator: YES
Seems to work fine if complete absolute path to the script file is specified
Logged In: YES
user_id=2071294
Originator: NO
I confirm this problem.
I am able to get the script to run the preconditions but won't continue on with the rest of the process.
I would really appreciate this being fixed asap as I am in the process of creating an automated build process.
Logged In: YES
user_id=2071294
Originator: NO
Yes it does work with fully qualified path to the script. Should've tried that!!!
A work-around is to specify a relative path to the current directory, e.g.:
instead of command:
"..\..\..\Inno Setup 5\istool\istool.exe" -compile Setup.iss
use:
"..\..\..\Inno Setup 5\istool\istool.exe" -compile .\Setup.iss
The .\ prefix does the trick. If not used, ISTool attempts to include the project file name to the output path as a directory, e.g.:
C:\MyProject\Setup.iss\Output\
and this - of course - must fail.
Regards
Tomas
instead
"c:\Program Files\ISTool\ISTool" -compile makesetup.iss
write
"c:\Program Files\ISTool\ISTool" -compile "makesetup.iss" (double quote ISS file)