Hi, would appreciate a hand with the following behavior.
Using a trial Enterprise version of IA v14.4
Builds: Single EXE setup (resources inside)
Themes: Style9green, Settings: Use Enhanced User Interface: Always (install, uninstall and maintenance)
run the following:
.\"BootstrapperInstaller.exe" /i \\ /l*v "InstallLog.txt"
InstallLog.txt contains the following:
=== Verbose logging started: 11/16/2017 16:25:41 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Users\InstallerBldr\Desktop\Advanced Installer Proof of Concept\BootstrapperInstaller.exe ===
MSI (c) (78:90) [16:25:41:403]: Note: 1: 2203 2: \ 3: -2147287037
MSI (c) (78:90) [16:25:41:403]: MsiOpenPackageEx is returning 3.
=== Verbose logging stopped: 11/16/2017 16:25:41 ===
Does this still relate to the Enhanced UI issues from 2012?
viewtopic.php?f=2&t=23711&p=60494&hilit ... eEx#p60494
viewtopic.php?f=2&t=23076&p=58128#p58106
https://www.advancedinstaller.com/user- ... ed-ui.html
Or is there something I'm missing with my command line arguments to the bootstrapper? We need to be able to pass command line args down into the internal bundled msi in order for all our legacy test automation to work. Getting some advice on this would be great thanks.