codesynergy
Posts: 100
Joined: Fri Nov 14, 2014 10:29 pm

Enhanced UI and Command Line Parameters

Hello,

This is the second issue I'm running into since the Enhanced UI (EUI) change (reference:http://www.advancedinstaller.com/forums ... hp?t=34215 ). I have the following batch file:

Code: Select all

REM Path to the installer executable
SET SetupPath="C:\Users\spero\Desktop\Install64\Statistica 14.0.9 64-bit.exe"

REM Installation Keys
SET SerialNumber="XXXXXXXX-X"
SET ProductKey="123456789-0"
SET InstallCode=""

REM Registration Information
SET FirstName="John"
SET LastName="Doe"

REM Installer log file
SET Log="C:\users\spero\desktop\log.txt"

REM Set value to "/qb" (without quotes) to make slient
SET SILENT_INSTALL_FLAG=

REM For testing only.
SET B_DEBUG_MODE=0

%SetupPath% SERIALNUMBER=%SerialNumber% PRODUCTKEY=%ProductKey% INSTALLCODE=%INSTALLCODE% FIRSTNAME=%Firstname% LASTNAME=%LastName% B_DEBUG_MODE=%B_DEBUG_MODE% /l*vx %Log% %SILENT_INSTALL_FLAG%
PAUSE
Consider the results I'm seeing when comparing the standard UI vs EUI and silent vs non-silent install:
CommandLineCompare.PNG
CommandLineCompare.PNG (65.43 KiB) Viewed 5579 times
Take a look at the "INSTALLCODE" property in the "EUI, Silent" section. The value is not being passed in correctly. The property name and value of the following property ("FIRSTNAME") is being set as the value of the "INSTALLCODE" property. This only appears to be an issue in the one scenario (EUI, Silent). This issue does not occur in the installer that I built before the EUI changes (AI 13.2 or 13.4).

Is this a bug, or has the method of passing in properties changed? I noticed that this issue only occurs with the property that is not defined. Passing in an empty string (INSTALLCODE= " ") seems to resolve the issue. But, obviously there is a consistency issue here, as all other scenarios accept a non-defined property as a paramater just fine. All the logging info is attached.


Thanks.
Attachments
Comparison.zip
(219.4 KiB) Downloaded 415 times
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Enhanced UI and Command Line Parameters

Hello,

Unfortunately this is a bug. I have tested your scenario and I can reproduce and confirm this issue. A fix will be available in a future version of Advance Installer, thank you for bringing it to our attention.

We will update this thread as soon as the fix will be out.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
codesynergy
Posts: 100
Joined: Fri Nov 14, 2014 10:29 pm

Re: Enhanced UI and Command Line Parameters

Thanks for the update.

This is why I think the option to disable the EUI should be put back in. Issues like this and the feature disablement issue (http://www.advancedinstaller.com/forums ... =2&t=34248) are more likely to pop up. The Windows Installer/MSI technology is ... finicky to begin with, and adding a layer of complexity on top of it only leads to more problems.

Anyways, that's just my two cents.


Thanks.
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Enhanced UI and Command Line Parameters

Hello,

This was fixed in version 14.1 of Advanced Installer released on June 30th, 2017.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”