Using Custom Settings for V13 SP2 Deployments

Date: 8 October 2014
Product/Release: Visual LANSA V13 SP2
Abstract: Using Custom Settings for V13 SP2 Deployments
Submitted By: LANSA Technical Support

Visual LANSA deployments allow users to create an Application that install via MSI.

Introduced in V13 SP2 was the file CustomSettings.wxi that allows for some customisation of how the MSI will run. The location of this file is: <lansa>\x_win95\x_lansa\x_apps\x_wix\source\CustomSettings.wxi

This contains source for four different settings that can be turned on or off, simply by changing the number from 0 (off) to 1 (on) or vice versa. This has the benefit of not having to add the options to the command line when running the installation.

Example of the four different settings

A. ShowExecApp

ShowExecApp sets whether the <Start Application> checkbox option is to be shown or not, after the installation has completed. It is very useful for giving the user the option as to whether they wish to run the application or not. Alternatively, you can take that option away from the end user and either have it run or not without prompting the user. This can be done in co-ordination with the next two settings. Note, if you have this turned on (set to 1), then by default, the check box will be selected regardless of the next two settings.


B. LaunchApplication

LaunchApplication is an option to have the application run straight after the install has completed, before the user has exited the install dialog. This is a good to use for client applications that have a high reliance on UI.


C. LaunchApplicationWhenFinishClicked

LaunchApplicationWhenFinishClicked will control whether or not  the application is to be launched when the you click the Finish button on the exit dialog. Turning this off is useful when there is no UI for your application, for example, if you are deploying a Server installation.


D. SkipLicenseDlg

SkipLicenseDlg gives the option to pass through without displaying the End-User License agreement.
Note: Adding this option means that the user automatically agrees to the terms and conditions.


In all cases when you are trying various or new types of deployments it is always crucial to test thoroughly before distributing your package.