Page History

...

1. Create SETUP.TXT yourself and specify the MSI parameters, including all the X_RUN parameters exposed as MSI Properties.
   
   
2. The SETUP.EXE can be replaced and perform whatever install the developer desires
   
   
3. Use a different Application Name than the one it was built with - for multi-client support at different Package levels. For example, Application built as LANSAInventoryControl could be put in directories Customer1InventoryControl and Customer2InventoryControl. These can then be maintained at different levels even though they are running exactly the same software. They can also be given different Patches too. (This option is not compatible with Feature Set Deployment)

Example setup.txt files

1.   /qb
   Displays a progress dialog only for both MSI and MSP installs and no confirmation dialog. Thus the installs happen automatically without any user interaction. MSI installs will use the settings from the previous install.
   
   
2.   /l*vx %TEMP%\InstallLog.txt
   Diagnostic log file output to user's temporary directory.
   
   
3.   /qf
   Displays a full user interface which overrides the default Patch behaviour of /passive and also overrides the Silent Install setting inside the MSI/MSP.