Page 2 of 2
Posted: Tue Sep 13, 2005 8:35 am
by sinan
Yes, for both these reasons, it is recommended that you write to seperate file, other than the default log file.
For instance, you could log to $LOGGED$.extra.log
Posted: Tue Sep 13, 2005 10:32 am
by zchris
OK. I think I'll add a suggestions to the list
I also noticed that when I specify the /l command line paramter that my setups are very very slow (e.g. 60 seconds vs. 5 without /l). Could you take a look at that? Thanks!
Posted: Tue Sep 13, 2005 12:10 pm
by sinan
That's normal...logging does write a lot of data. We also flush the log file to further aid in debugging (in case it crashes and looses log data). So logged setups...will be slow.
Posted: Wed Sep 14, 2005 5:38 am
by zchris
Hmm, in that case I will create my own logfiles.
Do you think that logging $SUCCESS$ and $LASTERROR$ will be sufficient or are there any other variables that could be of interest?
Posted: Wed Sep 14, 2005 5:43 am
by sinan
That's a tricky question, really. Windows Installer logs contain a lot of information that is often useless, but sometimes for debugging a setup, you really need all that information.
Other than that...I think logging SUCCESS and LASTERROR would suffice, yes. In the cases it fails, you can always ask a customer to use the command line parameter for turning on MSI logging.