In reply to Rob's points: 1. I knew about the Burn log file Variables and link on the failure page. Since I'm new to both Windows Installer and WiX, I was hoping to avoid the need to write my own bootstrapper just to control logging. I may be installing to XP machines without .Net installed so I wouldn't even be able to write a managed bootstrapper. While I still occasionally program in C++, it is no longer my top choice for this sort of thing. Is there any possibility that this functionality could be added to the standard bootstrapper? If not, is wix36-sources\src\ext\BalExtension\wixstdba the place to start for writing my own?
You're right about the Bundle log file name being self-explanatory. The problem with TEMP is that someone may run Disk Cleanup or remove log files files using some other maintenance tools. 2a. The tips about "!" and "x" are helpful. I'll remove both of them. 2b. Since the installs are being done on customer machines by their own IT people, requiring a certain logging policy would be considered intrusive unless there was a serious emergency. The best I can hope for is a logging solution that will work with most logging policy settings, including the default. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-and-Msi-logging-revisited-tp7578871p7578878.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
