Hi,
I have been trying to improve on my BAT file (where I retain older Install.log files from prior installations), but I'm having a problem. Here is the latest BAT file which I know to be valid and doing waht I want because if I run the BAT file interactively after an installation it does what I need it to do in both scenarios (1, where the install.log file is not already present -that is, the Else logic is in effect-, and 2) when there is an Install.log file present).
Code: Select all
@echo off
REM usage: CopyInstallLog.bat [MSILogFileLocation], [AppDir]Install.log
IF EXIST %2 (
rename %2 Install_Hist.log
copy Install_Hist.log + %1 %2
erase Install_Hist.log
goto END
) else (
copy %1 %2
goto END
)
:END
pause
ADDENDUM: I think the code above should work but it's a bit uneasy with the UAC issue of a Limited User doing an Update install when they don't have any rights in the AppDir folder.
The problem I'm having is that when I include this BAT file as a Custom Action during my testing I do not see it having the desired effect. It is almost as though the Custom Action or BAT file is no longer being called during the final step of my installer. I have attached a sample MSI LOG file so maybe you can see if what is wrong?
My Custom Action > Launch File settings look like this:
> Properties
File to Launch: [#CopyInstallLog.bat]
Command Line: "[MsiLogFileLocation]" "[APPDIR]Install.log"
Working Directory: [APPDIR]
(checked) Hide program's window
(checked) Run As Administrator
> Execution Time
Immediately
> Execution Options
(checked) Wait for custom action to finish before proceeding
FOLLOW US
Get the latest news in Application Packaging