Each component must be named in the component directory description file and associated with the component implementation file. The binding between a given component and this file is established by the component description file. A single component template file can describe multiple custom components, and a single object library, executable program, or script file can contain the implementation for multiple custom components.
A component description file uses the Windows INI file format. The following is a sample component description file specifying two components that use the same implementation and template files:
[info]
list=ComponentOne,ComponentTwo
clientarchitectures=All
serverarchitectures=All
vendor=Microsoft
contact=http://www.microsoft.com
version=0.1
serverbinding=stdio
servermodule=newbots.pl
clientbinding=BTL
clientmodule=newcomponents.htm
[ComponentOne]
name=New Component One
description=something or other
type=insert
[ComponentTwo]
name=New Component Two
description=something or other
type=insert
The component description file must contain an [info]
section; its keys apply to all of the components in the directory. If the directory contains only one component, then all of the keys can go into the [info]
section. If there are multiple components in the directory, each one must have a separate section with the same name as the component.