The TICS setup program for the TICS client installation can be
customized and made silent by specifying a special
<setupname>.ini file. When a
<setupname>.ini file is available that
satisfies the conditions below,
the setup executable will read this file at startup of the installation
process. All options that are set in the
.ini file are used
to skip steps of the installation process that would otherwise be
interactive. Furthermore, other options can be set in the
.ini files to change specific behavior. See the properties
below for more details.
<setupname>must have the following format:
ticssetup-<version> where <version> must be a proper TICS version number, e.g.,
7.0. If the TICS setup executable has not been renamed, the
.inifile has the same name as the setup executable name with the
.exeextension replaced by
.inifile is located in the same directory as the setup executable.
.ini is present in the same directory as the TICS setup
.ini can be ignored by running the TICS setup program
/noini command line option.
Each setup can be run completely in silent mode, i.e. no dialog is shown
at all by running the setup with the command line option
/S. When no .ini file is specified the default values will
be used to install, otherwise the properties set in the .ini will be
The TICS client installer installs TICS plugins for all tools that have been detected automatically on the target system. For tools for which it is not possible to know whether they have been installed (e.g. because their installation is not administered in the registry), a facility is offered to enforce the installation of these TICS plugins in the .ini file:
Since Eclipse installation information is not stored in the registry, TICS must explicitly ask for it. If the Eclipse installation location is known beforehand, it can be specified with the InstallPath variable in the Eclipse section:
Since IntelliJ installation information is not stored in the registry, TICS must explicitly ask for it. If the IntelliJ installation location is known beforehand, it can be specified with the InstallPath variable in the IntelliJ section:
For NetBeans the TICS plugin files must be copied to some location in order to import them in the NetBeans IDE. If there is a default NetBeans installation directory, it can be specified with the InstallPath variable in the NetBeans section:
To install the TICS Tornado plugin the installer needs to know where the Tornado IDE is located on the file system. Unfortunatelly, it is not possible to do this automatically. If the Tornado IDE is installed in the same location for all users, it is possible to preconfigure the location of the Tornado IDE in the .ini file. This can be done for Tornado 2.0 and Tornado 2.2 IDE installations.