Hello,
I am able to use Write To Text file $LOGGED$ when I compile the Installaware installation into an exe, but when I compile to an MSI this does not seem to work. I have tried all the variations for MSI logging but still cannot figure out to get the Write To Text file $LOGGED$ to appear in the logs generated from the MSI installation routine.
Write To Text file $LOGGED$
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Write To Text file $LOGGED$
Dear FabSter,
you should use the following form with a MSI package in order to assign the "LOGGED" predefined variable.
- msiexec.exe /i "C:\mysetup.msi" CMDLINE="LOGGED=C:\mylog.txt"
However if you have a look at IA documentation about "Logged Execution", you will see;
"With the Windows Installer engine, logged execution will create a log file and record both the internal state of the installation (along with all variable values) and the native Windows Installer log inside a plain text file. Since all changes are pending until Apply Changes is called, the log will be created only after Apply Changes has been called."
Due the above behavior with a MSI package, the MSI log takes the precedence over any other "custom" log data and it will also replace any custom data which may have been already stored to the log-file before of "Apply Changes" execution. Please also note that MSI engine does not provide the possibility to store custom log data with the MSI log itself.
With an EXE package instead and due the InstallAware engine capabilities, this doesn't happen.
Hope this helps you.
Regards
you should use the following form with a MSI package in order to assign the "LOGGED" predefined variable.
- msiexec.exe /i "C:\mysetup.msi" CMDLINE="LOGGED=C:\mylog.txt"
However if you have a look at IA documentation about "Logged Execution", you will see;
"With the Windows Installer engine, logged execution will create a log file and record both the internal state of the installation (along with all variable values) and the native Windows Installer log inside a plain text file. Since all changes are pending until Apply Changes is called, the log will be created only after Apply Changes has been called."
Due the above behavior with a MSI package, the MSI log takes the precedence over any other "custom" log data and it will also replace any custom data which may have been already stored to the log-file before of "Apply Changes" execution. Please also note that MSI engine does not provide the possibility to store custom log data with the MSI log itself.
With an EXE package instead and due the InstallAware engine capabilities, this doesn't happen.
Hope this helps you.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Re: Write To Text file $LOGGED$
Thanks that worked perfectly;)
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Write To Text file $LOGGED$

Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Who is online
Users browsing this forum: No registered users and 121 guests