msiexec log/lv VS/l*v 的区别 [英] Difference between msiexec log /lv VS /l*v

查看:29
本文介绍了msiexec log/lv VS/l*v 的区别的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述



关于日志记录的一些预先存在的答案:

Microsoft's documentation for msiexec says this:

/lv Turns on logging and includes verbose output in the output log file.

/l* Turns on logging and logs all information, except verbose information (/lv) or extra debugging information (/lx).

Examples To install package C:\example.msi, using a normal installation process with all logging information provided, including verbose output, and storing the output log file at C:\package.log, type:

msiexec.exe /i "C:\example.msi" /L*V "C:\package.log"

I think it might help to have an example installer log. What is 'all logging information' vs verbose logging? Isn't verbose just that & historically shows all logging info? Guessing this is going to be a unique Microsoft thing

解决方案

Debug Logging (Verbose): Advanced, slow logging for maximum details captured. This is - as far as I can tell - the most information you can capture in an MSI log:

msiexec.exe /i C:\Path\Your.msi /L*vx! C:\Your.log


Interpreting MSI logs: MSI log files can be very verbose indeed. Advanced installer and an old blog from the MSI team of many years ago have a few clues to their content:

This old dialog from a log-command generation tool might help. The flush to log means the log is written directly and continuously and not in batches. This continuous writing slows things down a lot, but no log buffer is lost if there is a crash:


WiLogUtl.exe: The Windows SDK contains this tool to analyze MSI log files. It can be helpful, although it is quite old-fashioned to look at GUI-wise. Search for it under: C:\Program Files (x86)\Windows Kits - if you have Visual Studio or the Windows SDK installed. Here is a screen shot:


Some pre-existing answers on logging:

这篇关于msiexec log/lv VS/l*v 的区别的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆