I don't think you can set the log file using MsiLogFileLocation. I think it
*gets* set to the log file location. You can force your package to require
MSI 4.0 by setting the Package/InstallerVersion attribute.
On Wed, Mar 14, 2012 at 9:10 PM, Alec Swan alecs...@gmail.com wrote:
Hello,
I need
I don't know if this is common knowledge but I don't set the MsiLogging
property anymore. There' s a known bug in Windows 7 where Explorer / Shell
can lose reference to the installer log file location and it causes the
installer to crash out.It can manifest itself on uninstall which means
The following thread implied that the file log location can be set
through MsiLogFileLocation property in WIX:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Msi-Logging-td707004.html#a707011
But it sounds like Rob is saying this is not possible.
So, how can I reliably enable MSI
I've seen the same bugs CP has seen. I've got it set in my installers, but
only because CD demands it. Setting it causes a fair number of install
failures, particular in install/repair/uninstall cycles.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Alec,
As far as I know, you can't set the log file location inside WIX because
you need to tell msiexec where to write the log file to before actually
starting the MSI. You need some sort of bootstrapper that calls msiexec
with the logging options. I've used IExpress in the past, but I think
Adam,
This post indicates that it is possible to set MSI property from WIX:
http://blogs.technet.com/b/alexshev/archive/2009/05/16/from-msi-to-wix-part-23-dll-custom-actions-logging-and-setting-properties.aspx
If this is true, shouldn't I be able to use this approach to set some
kind of MSI
You can't set MsiLogFileLocation, as the MSDN docs pretty much say. You can try
to set it but it's ineffective. If you set it in the property table it just
gets overwritten. If you set it with a type 51 it just gets ignored.
Phil W
-Original Message-
From: Alec Swan
Phil, thank you for sharing your experience.
I would like to keep this thread active until we get a definite answer
from the WIX team. Whether it is You can't enable MSI logging in the
current version of WIX but will be available in version x.x or This
is how you do this ... - it will still be
Given that WiX generates MSI files and the MSI MSDN docs say you can't set it,
and my testing also indicates that you can't set it, I don't see how you could
expect a different answer from the WiX Team! It's nothing to do with WiX, or
InstallShield or any other tool that generates MSI files.
WiX is not in control of the MsiLogFileLocation property. This is functionality
provided by Windows Installer.
As mentioned earlier, the log file location must be set before the MSI package
is loaded by the Windows Installer engine. This is how Windows Installer works
and the WiX team has no
I was also going to point out that Rob already responded with the same info and
you don't get much more WiX Team than that.
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Thursday, March 15, 2012 11:07 AM
To: General discussion for Windows Installer XML
A good test anyone can try. Run a command something like this.
MSIEXEC.EXE /L*v C:\Foobar\test.log /I path to MSI
For that log folder that you point to make sure the C:\Foobar directly DOES NOT
EXIST.
Note how MSIEXEC.EXE will simply error out rather than creating the Foobar
folder in which
Hello,
I am fairly new to WiX. I have an installer which installs standard
components and has one optional feature, feature X. If I run the installer
everything works as expected for a basic install with or without feature X
included. If I run the installer again and select Change in
In addition, the Windows Installer engine starts producing log messages before
it loads the MSI package to determine what log file to use.
In short, one can set a log file:
* On the command line
* As an argument to MsiProductInstall()
* In the registry (global and applies to all MSI packages,
I just realized that the thread I am looking at says explicitly that this is
still a bug in v3.5.
It also mentioned a workaround, but I can't figure out exactly what it
means:
The work around in WiX v3.0, unfortunately, is to pull the second ProgId
out
and set its registry keys using
Wow, this is a pretty active mailing list. I think we have the
definite answer now.
As you can already tell I am a newbie to WIX, so please take it easy
on me with my next question. What logging mechanism do you normally
use to log messages from your custom actions?
Thanks,
Alec
On Thu, Mar
I use a second custom action called WriteToMSILog that I call at specific times
from my first custom action to log to the normal log file that everything else
writes to. Keeps everything in one log file and is easy to call as needed.
The CDATA portion looks like this (Jscript example)
