Hi Sascha - Thanks for the example code. I understand the out-of-scope handle problem, and I don't save one and use it for something...I just mentioned that in the previous post to see if it made a difference during debug.
My code does work, until after install. I can log all day, but not after installation is (almost) complete. I display a configuration dialog after the files are installed, and prior to the final WiXExitDlg. During that time I can't write to the log, and I just happened to notice that the MSIHANDLE changed. I just don't understand why I can't log at that time. The MsiProcessMessage function returns "no action taken"... wtf? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unable-to-log-through-DLL-using-MsiProcessMessage-tp709471p5189352.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
