Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Normally, to enable logging, you’d say msiexec ... /l*v [or any other combination].
You can also enable logging all products via the registry tweak.
Note that these are all outside actions, in a sense that the wxs script is not the one specifying the logging options.
Is there a way to control logging from within the wxs script? Preferably to a folder like INSTALLDIR\Logs?
Is this a good practice? I know uninstalling will leave the Log folder behind, unless I clean it up somehow.
You can request a log verbosity level with the MsiLogging property. However, you can’t control where the log is created and both level and location are overridden by anything the user specifies.