| 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
-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
| 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
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
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 |
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
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
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
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 |
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
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
11 matches
Mail list logo