Updated: November 2007
Runs a transform on a specified text template file from the command line. For more information, see Command-Line Tools for Text Templates.
TextTransform [<options>] <templateName>
Argument
Description
templateName
Identifies the name of the template file that you want to transform. For more information about how to create a new text template, see How to: Create Text Templates.
Option
-out <filename>
The file to which the output of the transform is written.
-r <assembly>
References an assembly for compiling and running the text template.
-u <namespace>
Imports a namespace for use within the template.
-I <includedirectory>
Provides a directory containing text templates included from within the specified text template.
-P <referencepath>
Provides a directory to search for referenced assemblies specified within the text template or for using the -r option.
-dp
Specifies the name, full type name, and assembly of a directive processor that can be used to process custom directives within the text template. The dp option looks like this:
-dp "<ProcessorName>!<ClassName>!<AssemblyName|CodeBase>"
-a
Specifies a parameter that a directive processor can query for as a name/value pair. The directive processor and identifier are optional. This allows parameters to be specified for any directive processor or any instance of a particular directive processor.
-h
Provides help.
TextTransform.exe is located in the <root>\Program Files\Common Files\Microsoft Shared\Text Templating\1.1 directory of your Domain-Specific Language Tools installation.
For more information, see Security of Text Templates.
If you are using TextTransform.exe with the -a option for passing a parameter to a directive processor, and you have created your own directive processor, the directive processor must call the ITextTemplatingEngineHost.ResolveParameterValue(string,string,string) method in order to get access to the parameters.
Parameters specified within the directive processor declaration on a text template are available separately to the directive processor by examining the "arguments" parameter of the DirectiveProcessor.ProcessDirective(string directiveName, IDictionary<string,string> arguments) method.