As a UI based installer, this works. The install log shows:
Code: Select all
//GUI STAGE
ReadINI : 10/3/2016 1:48:27 PM setting session property SERVER_INSTALL to 1
.
.
//INSTALL STAGE
MSI (c) (A0:28) [13:48:54:145]: Feature: Client; Installed: Absent; Request: Local; Action: Local
MSI (c) (A0:28) [13:48:54:145]: Feature: Server; Installed: Absent; Request: Local; Action: Local
MSI (c) (A0:28) [13:48:54:145]: Feature: Common; Installed: Absent; Request: Local; Action: LocalCode: Select all
//INSTALL STAGE
MSI (s) (8C:80) [12:23:15:127]: Feature: Client; Installed: Absent; Request: Null; Action: Null
MSI (s) (8C:80) [12:23:15:127]: Feature: Server; Installed: Absent; Request: Null; Action: Null
MSI (s) (8C:80) [12:23:15:127]: Feature: Common; Installed: Absent; Request: Local; Action: Local
.
.
ReadINI : 10/3/2016 12:23:16 PM setting session property SERVER_INSTALL to 1I realize that there is an "ADDLOCAL" option to pass to the MSI - but that requires knowing the runtime requirements BEFORE runtime. Obviously I can't tell the future... it needs to be resolved at run time.
Is there anything that can be done to push the execution of the VBS higher up the INSTALL stage, so that the features are determined at run time prior to copying of files?
FOLLOW US
Get the latest news in Application Packaging