This tab of the Transform XML Log action specifies information about the file to be processed.

 

Input file: The source XML log file or document to process (required).  This can be a Visual Build XML log file or any other valid XML document.

 

Close input log file XML tags: If checked, any missing step, build, or log elements are added to the input file before processing to ensure that it is a valid XML file.  The changes are made on a copy of the input file so that the original log file is not affected, and the XSLT stylesheet (if specified) is then applied to the copy.

 

Preserve white space: If checked, preserves white space in the document.

 

Do not validate DTD or schema: If checked, the document will not be validated against a document type definition (DTD), schema, or schema cache.

 

Do not resolve external definitions: If checked, external definitions, resolvable namespaces, DTD external subsets, and external entity references will not be resolved at parse time, independent of validation.

 

Prohibit inclusion of a DTD: Determines whether inclusion of a DTD is allowed or prohibited.

 

Enable XSLT script code execution: Determines whether <msxsl:script> element functionality is allowed.

 

Enable document function: Determines whether the document function is allowed.

 

Use inline schemas for validation: Determines whether inline schemas should be processed for validation.

 

XSLT stylesheet: The XSLT stylesheet to apply to the document (optional).  Leave blank if no stylesheet should be applied (to close the XML log tags on the log file).  Some default XSLT stylesheets are provided in the Style subfolder of the installation path:

 

Also, any valid stylesheet can be specified (although in order for filtering of log output to function correctly, the stylesheet's param tags must be supplied and used in the same manner as the default stylesheets).

 

Note: The default stylesheets can be modified by the user (to change the document layout, fonts, colors, etc.), but any changes should be saved under a different filename, since the default stylesheets will be overwritten when updates to Visual Build are installed or if it is re-installed.

 

Include nested (chained) build steps: Determines whether step output for nested builds will be included in the HTML report.

 

Output file: The destination filename to generate (required).

 

Note: To make the XML or HTML build log file accessible to other users, simply map an IIS or other web server virtual directory to the path containing the log or HTML files, and the log files can be accessed via any web browser.

 

Format (indent) document: Whether to format (indent) the XML document.

 

Encoding: The encoding for the formatted XML file (applies only when formatting).

 

Display output file: Indicates that the resulting output file should be launched in its associated application.