Re: [WiX-users] Using Lux and Nit

2014-10-11 Thread Bob Arnson
On 11-Oct-14 12:59, Phill Hogland wrote: > This results in NIT8104: Package Failed: Fatal error during installation Yet another bug. The Lux custom actions are written in DTF and they aren't set up for .NET 4.0. I have a pull request ready: https://github.com/wixtoolset/wix3/pull/160 -- sig://b

Re: [WiX-users] Use of MsiLogging in Burn driven MSI

2014-10-11 Thread Rob Mensching
It would be reasonable for Burn to respect the MsiLogging property in the MSI like it does MSIFASTINSTALL and such... if you wanted to open a feature request. _ Short replies here. Complete answers over there: http://www.firegiant.com/

[WiX-users] Unsubscribe.

2014-10-11 Thread Rob L
Unsubscribe thanks for the help. -- 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? Do

Re: [WiX-users] Using Lux and Nit

2014-10-11 Thread Phill Hogland
Thanks for the info. I started over with a new VS2013 msi setup template project. I added code, essentially from Rob's remember property pattern post, and then used the same command line file I shared earlier. I now get further down the path successfully producing the xxx_test.msi (and not seein

Re: [WiX-users] Use of MsiLogging in Burn driven MSI

2014-10-11 Thread Phill Hogland
Thank you for the feedback John and Bob. I appreciate it. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Use-of-MsiLogging-in-Burn-driven-MSI-tp7597242p7597253.html Sent from the wix-users mailing list archive at Nabble.com.