The keys stored in the component description file
[info]list
A list of component shortnames (separated by commas) enumerating the components in this directory. The shortnames must be unique across all components in the web. An easy way to do this is to add a company name to the beginning of the name of the component. This is an optional parameter; if not present, there is only one component in this description file (whose shortname is the basename of the info file) and all keys are in the [info] section.
serverarchitectures
Reserved for future use. This is an optional parameter. If present, the value should be “All”.
clientarchitectures
Must be present for the client to be able to insert a new FrontPage component of this type into a page. For this release, the value should be either “All” or “WinI386”. If you set the clientBinding key (see below) to type “DLL”, you should use “WinI386” so that only Windows clients will download the module. For a clientBinding of type “BTL”, you should use “All” so that any client can use it. You should always provide a BTL binding in addition to any DLL binding, so that all FrontPage clients can use the component. This key is mandatory for the client and optional for the server.
version
A version number, which can be an integer or decimal number. This is a mandatory parameter. The FrontPage client compares the FrontPage component’s version number in the \botcache directory with the version number reported by the FrontPage server during a recalculate links or open web operation. The client will not download a fresh DLL from the server unless the version number on the server is greater than the version number cached on the client. To make sure all clients will recognize a new version of a FrontPage component DLL, you should increment the FrontPage component’s version number (even if it is by .01) and do a Recalculate Hyperlinks operation in FrontPage.
vendor
The component vendor’s name. This is an optional parameter.
contact
How to contact the vendor (by URL, telephone, and so on). This is an optional parameter.
serverBinding
The method for interfacing with the server-side implementation. Possible values are “DLL” or “Stdio”. This is a mandatory parameter if this directory includes a component implementation file.
serverModule
References the server-side implementation file (library, executable file, or script). This is a mandatory parameter if this directory includes a server-side implementation.
serverInterpreter
If the serverModule is a script (which implies that serverBinding must be Stdio) and the server OS cannot auto-execute scripts (such as Windows) then this key identifies the script interpreter. If this directive is present then instead of executing serverModule, FrontPage will execute serverInterpreter and pass it to serverModule as its first argument.
clientBinding
The method for interfacing with the client-side implementation. There are two possible values: “DLL” or “BTL” (Bot Template Language – described below). This is a mandatory parameter if this directory includes a client-side implementation.
clientModule
References the client-side implementation file. This is a mandatory parameter if this directory includes a client-side implementation. This points to the file containing the template or the DLL. For convenience, template files usually have a .htm extension.