21.1 Windows Installer File Install

When you successfully build a Version a Version Installer file will be produced. This will include all the objects required to install your application whether it be a server installation, a client installation, a network client or other variation.

Similarly, if you build a Patch, a Patch Installer file will be produced. The Patch Installer file must be installed on top of an Application which has previously been installed using a Version Installer file. In the case of a Patch install, only new or modified objects will be installed. Any unmodified objects included in the Patch will not be reinstalled. Whether an object has been modified is determined based on the DLL File Version Number of the shipped DLL. Refer to Set DLL Version Information for more detail.

The products of the Deployment Tool build process, the msi and msp files, are automatically associated with the Microsoft Windows Installer process (msiexec.exe). To start the installation, you can:


All Deployment Tool installations automatically log their installation behavior to an MSI*.log file in the installing user's defined %TEMP% folder, for example: MSI2ce4c.log. There are also other LANSA-specific log files with the general format of LansaInstallLogMSI*.txt. When reporting an issue to LANSA Support please supply all these files to expedite the process. Note that when using the Remote Desktop Program, there may be log files in the parent directory of %TEMP%. And when deploying into the Cloud, log files may be found in c:\windows\temp.

As well as installing the Application, a standard Windows program menu folder will be created for each Application using the Company and Application descriptions as folder names. This means that every Application built with the same Company details and installed on the same PC will be grouped together.