Setup/Uninstall: Allow automatic output redirection to installation log
Right not logging the output of command run during install is not very nice, you would have to run the tool through cmd and manually redirect the output to a file. Maybe even have to manually check if log has been requested on install and redirect to nul if it hasn't.
All these makes it a little harder to maintain a install script (maybe you just forgot to put the whole command inside quotes, etc).
So, having a way to redirect command output to the main log file or to a custom log file, as an option for each command run or at installer level would be a great feature which will increase usability and productivity of the one making the install script.
Sebastian Schuberth commented
FYI, I'm working one something similar over here:
I'm targeting at showing the console output inside the setup GUI, but of course it can be redirected to a file, too.
Martin Baschnegger commented
It would also be interesting if it is possible for processes that are created via DLL-API and CReateProcess(Win32) to redirect their stdout+stderr to the logfile.
liviu trifoi commented
Yes, I definitely agree with that. It would be nice especially for vb scripts that are called from inno setup, in order to log any errors they throw directly into the inno setup log, and would be a good idea for all other utilities that are called and wish to log actions performed during install. It's tedious to redirect.