The text template transformation process takes a text template file as the input, performs the transformation on the input, and generates a new text file as the output. The engine component controls the process, and interacts with a text template transformation host and one or more text template directive processors to complete the process. For more information, see.
The text template transformation process has two steps. In the first step, the text template transformation engine creates a class that is referred to as the generated transformation class. In the second step, the engine compiles and executes the generated transformation class, to produce the generated text output. The generated transformation class is comprised of the code of the text template, that is, the statements, expressions, class features, and boilerplate text in the text template, and the results of calling directive processors. For more information, see.
Advanced users might want to implement their own text template transformation engine host or directive processors.
For more information, see:
|AssemblyCacheMonitor||Monitors the state of the assembly cache.|
|DirectiveProcessor||The abstract base class for a concrete directive processor.|
|DirectiveProcessorException||The exception that is thrown by the text template transformation engine, if an error occurs while processing directives.|
|EncodingHelper||A utility class that gets the encoding of a file from its byte order mark.|
|Engine||The text template transformation engine.|
|RequiresProvidesDirectiveProcessor||The abstract base class for a directive processor that defines and implements a design pattern called requires/provides.|
|TextTransformation||The abstract base class for all generated transformation classes. This class also provides utility methods and properties for use in text template code.|
|ToStringHelper||A utility class that is used to produce a culture-specific representation of anas a .|