Preventing Confidential Information from Being Written into the Log File of MSI during debug

lots of our installations are getting password as input parameter in the command line, the problem was that since we install using debug logs (coz we want easier support of failing installation) the password was written to the log file

The problem was created because we only added support for the password as command line argument but didn't add the dialog to support UI mode also and apparently if the property you use is associated with control that is set as password than its not written to logs (no matter what)

This is a well known issue that we simply missed :(

See the following article in MSDN that clearly state what should be done to prevent such cases (also in custom actions values)

So before you create a funny mechanism like find-n-replace on the logs, simply do the complete work