How IFS Configuration Builder Creates the Build

When the build process is executed, the tool copies files from a source directory into a build destination, <build_home>. The content of the components will be copied without any changes of the structure on top of each other. A sub set of options included in build process can be selected in the Select Build Options, as well as included languages.

Contents

Automatically Excluded Folders

The following folders will always be automatically excluded when building.

The following folders will always be excluded, also as subfolders, when building.

Automatically Created Files

File Target Path in Build Remark
<components>.ini database Includes information about the component, copy of components deploy.ini. Will be used when creating the install.tem file.
install.ini database Includes information about the components dependencies to other component as well as the installation control for each component.
<lng>.ini server\translation\clientLanguages Includes information if the specific language should be enabled for client runtime.
forcedelivery.txt client\runtime Can be created when running in silent mode, started from IFS Solution Delveloper (ISD) . When the file exist, and CompileDotNet set to Yes, a client delivery will allways be created, also when no new/modified client source code is included in the delivery.

Optionally Included Folders/Files