Files that comprise a new component
- Last UpdatedApr 24, 2025
- 1 minute read
Each new component is comprised of at least four files: AssemblyInfo, RPC<name>, <name>Processor, and a Process method example.
AssemblyInfo
This file contains information about the entire .NET assembly, such as feature information, version information, and an assembly Graphical User Interface (GUI). This file is also responsible for giving the assembly a strong name. Strong-named assemblies have a unique identifier and a private key that prevents tampering.
RPC<name>
This file implements the interface class for the component. The interface class is
responsible for exposing the component to the Business Logic Tier (
BLT) infrastructure. It contains an instance of the <name>Processor class, which performs
the business logic. The RPC<name> class is derived from the BLTComponent class, which
does all of the interface work for you. You should not need to modify this class.
<name>Processor
This file implements the <name>Processor class, which is derived from the BLTProcessor class. This class implements a Process() method, which is where you write the business logic. The constructor for this class defines the syntax for the component. The BLTProcessor class provides built-in properties and methods to assist you in writing the business logic code.
The C# version of this class is commented using special /// comment markers and XML tags. These tags are interpreted by the compiler to produce an XML documentation file, which can be processed by tools such as nDoc and the built-in Build Comment Web Pages tool to produce Windows Help files and HTML help files.