Hi all, How does one handle the situation where the Util:XmlFile custom action logs sensitive information to the log file?
Eg: MSI (s) (F8:8C) [11:43:03:072]: Executing op: ActionStart(Name=ExecXmlFile,,) MSI (s) (F8:8C) [11:43:03:074]: Executing op: CustomActionSchedule(Action=ExecXmlFile,ActionType=3073,Source=BinaryData,Target=ExecXmlFile,CustomActionData=2€0€C:\Program Files\ABC\File.exe.config€3€0€//configuration/connectionStrings/add[@name='ABC']€connectionString€User ID=user;Password='q9h581)D3]';) This message<https://www.mail-archive.com/wix-users@lists.sourceforge.net/msg54073.html> by RobM suggests that the situation is a bug. (Dec 2012) It looks like this issue was addressed previously (bug3859<http://wixtoolset.org/issues/3859/>), but the result was that it is not a bug by Bob Arnson (Oct 2013). I found the workaround hack of adjusting the Type in the CustomAction table for the ExecXmlFile Action after the msi is produced... Is this the only way? Thanks, Kevin ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
