Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-22 Thread Phil Wilson
| Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada -Original Message- From: Mark A. Richman [mailto:m...@markrichman.com] Sent: April-22-15 8:18 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Too Many

Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-22 Thread Mark A. Richman
-4674 Government of Canada | Gouvernement du Canada -Original Message- From: Mark A. Richman [mailto:m...@markrichman.com] Sent: April-22-15 8:18 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Too Many Events Using InstallLogModes I read the docs. None

Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-22 Thread Keith.Douglas
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada -Original Message- From: Mark A. Richman [mailto:m...@markrichman.com] Sent: April-22-15 8:18 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Too Many Events Using InstallLogModes I read

Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-22 Thread Mark A. Richman
I read the docs. None of what I've read so far shows which log level (InstallLogModes) will show/hide the following type of messages: MSI (c) (E8:30) [16:46:35:016]: Creating MSIHANDLE (28312) of type 790531 for thread 6448 MSI (c) (E8:30) [16:46:35:047]: Closing MSIHANDLE (28312) of type 790531

Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-21 Thread Mark A. Richman
Nir, I am using the Deployment Tools Foundation (DTF) API, not msiexec.exe from the command line. So, the voicewarmup parameters don't apply. I was asking specifically about the InstallLogModes enum. Thanks, Mark -- Mark Richman (954) 234-9049 1-954-234-9049 m...@markrichman.com |

Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-21 Thread Mark A. Richman
Do you know which flag(s) correspond to Creating MSIHANDLE and Closing MSIHANDLE messages? -- Mark Richman (954) 234-9049 1-954-234-9049 m...@markrichman.com | http://markrichman.com https://linkedin.com/in/mrichman On Tue, Apr 21, 2015 at 2:21 PM, Nir Bar nir@panel-sw.com wrote: It

Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-21 Thread Nir Bar
The (c) and (s) stand for (c)lient and (s)ervice- representing the scipt-generation phase (client) and the script execution (service) phase. You can check msiexec logging level options https://technet.microsoft.com/en-us/library/cc759262%28v=ws.10%29.aspx#BKMK_SetLogging . If you only need

Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-21 Thread Nir Bar
It doesn't really matter- the point is that Windows Installer supports these logging level regardless of how you triggered it, be it msiexec or DFT. These are also the same levels that MsiEnableLog https://msdn.microsoft.com/en-us/library/aa370091(v=vs.85).aspx has. - Nir Bar Freelance

[WiX-users] Too Many Events Using InstallLogModes

2015-04-21 Thread Mark A. Richman
Hi all, I'm currently logging everything using the following flags: const DTF.InstallLogModes logEverything = DTF.InstallLogModes.FatalExit | DTF.InstallLogModes.Error | DTF.InstallLogModes.Warning | DTF.InstallLogModes.User | DTF.InstallLogModes.Info | DTF.InstallLogModes.ResolveSource |

Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-21 Thread Phil Wilson
Seems unlikely to be the Terminate setting. This is the base documentation: https://msdn.microsoft.com/en-us/library/aa370573(v=vs.85).aspx that the interop is mapping to. --- Phil Wilson On Tue, Apr 21, 2015 at 1:39 PM, Mark A. Richman m...@markrichman.com wrote: I discovered

Re: [WiX-users] Too Many Events Using InstallLogModes

2015-04-21 Thread Mark A. Richman
I discovered that using InstallLogModes.Terminate is what's producing the verbose events...but why? -- Mark Richman (954) 234-9049 1-954-234-9049 m...@markrichman.com | http://markrichman.com https://linkedin.com/in/mrichman On Tue, Apr 21, 2015 at 2:26 PM, Mark A. Richman m...@markrichman.com