I tried to create an install with an install log by using the following command... after the apply install.
Apply Install (get result into variable SUCCESS)
Set Variable LOGGED to $TARGETDIR$\log.txt
But no log.txt file was created.
Is there another location I need this command ? What am I missing?
Thanks.. George
Logging
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Logging
Dear George,
To execute a logged setup, use the following command line:
<setup.exe> /l=<path to logfile>
Regards
To execute a logged setup, use the following command line:
<setup.exe> /l=<path to logfile>
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
-
- Posts: 63
- Joined: Sun Jul 13, 2014 3:28 pm
Re: Logging
This is all I see in the log file
<InstallAware>
<SupportDir>
</SupportDir>
<SetupSplash>
<StubSize>
</StubSize>
<StubData>
</StubData>
<GlobalLists>
</GlobalLists>
<ExtractArchive>
</ExtractArchive>
<ResourcePath>
</ResourcePath>
<Dialogs>
</Dialogs>
</SetupSplash>
<RunScript>
<Variables>
</Variables>
<CompileScript>
</CompileScript>
<BootStrap>
</BootStrap>
<myah>
What did I do wrong.
<InstallAware>
<SupportDir>
</SupportDir>
<SetupSplash>
<StubSize>
</StubSize>
<StubData>
</StubData>
<GlobalLists>
</GlobalLists>
<ExtractArchive>
</ExtractArchive>
<ResourcePath>
</ResourcePath>
<Dialogs>
</Dialogs>
</SetupSplash>
<RunScript>
<Variables>
</Variables>
<CompileScript>
</CompileScript>
<BootStrap>
</BootStrap>
<myah>
What did I do wrong.
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Logging
Dear George,
"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."
So if nothing appears in the log ... probably the "Apply Changes" statement is never executed.
Regards
"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."
So if nothing appears in the log ... probably the "Apply Changes" statement is never executed.
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
-
- Posts: 63
- Joined: Sun Jul 13, 2014 3:28 pm
Re: Logging
still confused. The apply install command is executed and all I see is what I posed on the 8th.
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Logging
Dear George,
if you are using a MSI based setup, this may depend by the fact that the "Apply Changes statement" (Apply Install, Apply uninstall or Apply Patch) is never executed in your script.
Instead using a NATIVE ENGINE based setup and If the pre-defined variable $DELAYUNTIL_APPLYCHANGES$ is TRUE, the log will be NOT written to as each setup command is executed individually; otherwise the log will be written to when Apply Changes has been called.
So even with this last case, if the "Apply Install" statement doesn't get executed the log will be not produced.
Anyway, without having your project I am not able to tell you much more.
If you want you could post a very MINIMAL project that replicates the issue.
Regards
if you are using a MSI based setup, this may depend by the fact that the "Apply Changes statement" (Apply Install, Apply uninstall or Apply Patch) is never executed in your script.
Instead using a NATIVE ENGINE based setup and If the pre-defined variable $DELAYUNTIL_APPLYCHANGES$ is TRUE, the log will be NOT written to as each setup command is executed individually; otherwise the log will be written to when Apply Changes has been called.
So even with this last case, if the "Apply Install" statement doesn't get executed the log will be not produced.
Anyway, without having your project I am not able to tell you much more.
If you want you could post a very MINIMAL project that replicates the issue.
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
Who is online
Users browsing this forum: No registered users and 116 guests