On 10-Oct-14 18:01, Phill Hogland wrote: > I have a chain of Burn driven MSIs. I implemented a MSILOGGINGVALUE property > (and related variable which Burn initializes and the mba overrides). If the > MSILOGGINGVALUE property is provided to the package I do a conditional > SetProperty action on MsiLogging, scheduled after LaunchConditions. But > regardless of what this property is set to 'iwearmo', 'voicewarmup', or > 'iwe', the resulting log is always supper verbose and larger than if there > is no MsiLogging property set in the MSI package (which is supposed to > default to iwearmo when the group policy and reg keys do not exist). Burn always creates verbose logs for MsiPackages.
-- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
