Output Details to Standard Output

[DTTerastar]

I've tried using the install.log but it's really really long and wordy. Helpful to fix bugs i'm sure, but impossible to find the actual reason for a install failure in my automated build system. I would a command line that outputs just the Details information to standard output when installing silently.

This would make the silent install much more usefull for continuous integration builds.

Thanks!

Darrell

[Anders]

Maybe you could call GetStdHandle with a custom plugin or the system plugin then output to that (Not sure if that works with a non CLI app) You might have to call AllocConsole first, I'm not sure

[DTTerastar]

I appreciate that you could do something very low level to make it work, but I really do believe that this should be a standard option. The silent mode is great, but losing all the details of what happened is NOT. And that install.log is not the same as just getting the details output.

[Red Wine]

Kichik's function from manual "D.4 Dump Content of Log Window to File" is the best that I know so far, though, it works for normal installations only.

[DTTerastar]

I read that one, but yes my installer is silent and needs to be silent.

[kichik]

You can have your installer parse the command line for a special switch that'd make it skip every page but the instfiles page. It'll be half-silent...

[DTTerastar]

Is that because all the logging goes through the GUI? There is no actual place to catch all the calls to log to the details? How about a hidden window on silent that can catch all the calls to write to the details and the installer can monitor the hidden window and write to standard out any new text.

[kichik]

All GUI logging goes through the GUI. The function used is update_status_text. You can't create a hidden window that'll catch it.