This works fine most of the time but I have run into one occurrence where the log could not be created in the root of C and so the installation didn't proceed. I presume it was a permissions issue. Regardless, I'd rather the log go to the [CommonFilesFolder]. I tried a command line argument of...Use the EXE boostrapper
Another approach is to create a log file by using the /L*V parameters in the command line of the Advanced Installer Bootstrapper. Also, these parameters can be always passed to the MSI when the package is launched through the EXE bootstrapper.
If you want your installation package to always create a log, you can follow these steps:
•open the Advanced Installer project of your installation package
•go to the Media page and select the Bootstrapper tab
•check the Create EXE setup file option
•set the MSI Command Line field to: /L*V "C:\package.log"
This way, when the user launches the installation through the bootstrapper, a log of the installation ("package.log") will be created automatically in the "C:\" drive.
Code: Select all
/L*V [CommonFilesFolder]"\myapp\install.log"
... but that gives an invalid command line error.
Any suggestions?
FOLLOW US
Get the latest news in Application Packaging