Debugger User Interface (XSLT)
For the latest documentation on Visual Studio 2017 RC, see Visual Studio 2017 RC Documentation.
This topic describes the debugger windows and dialog boxes. It only discusses the user interface pieces that have XSLT-specific debugging behavior.
For more information, see the Debugging User Interface Reference.
The Locals window displays information about any variables defined in the style sheet. The Locals window contains three columns of information:
This column contains the names of all local variables in the current scope. Node sets have a tree control that you can drill-down to see its subfolders.
This column shows the value contained by each variable. Attribute, processing instruction, comment, text, and CData nodes display the text value of the node. Namespace nodes display the namespace URI.
This column identifies the data type of each variable listed in the Name column.
The Locals window also displays the predefined context variables that track the context of the XSLT transformation. The following table describes the predefined context variables used by the XSLT debugger.
|The context size.|
|The position, or index number, of the context node, relative to the context size.|
|The value of the context node.|
For more information, see How to: Change the Debugger Context.
The Output window shows any error messages or security exceptions that occur during debugging.
The XSLT debugger uses a separate window to display debugger output. This is the same window used to display output from a Show XSL Output command.
The Task List lists all the compilation errors in the style sheet. Double-clicking the error takes the cursor to the line with the error.
The Task List includes any errors that occur in the script blocks in the XSLT file.
The XSLT debugger has no warnings, so they never appear in the Task List.
The Breakpoints window shows all breakpoints set in the current project. If a breakpoint is added while the window is in view, the window is automatically updated to show the new breakpoint.
The Breakpoints window should behave the same way as other Visual Studio debuggers.
Not implemented in this release of the XSLT debugger.
The Watch window is used to evaluate variables. You can also change the values of the variables.
The variables displayed in the Watch window are for the current context (the top-most item on the call stack). If you change the context, the watch window updates and displays variables set for that context.
The Call Stack window is used to view the names of functions on the call stack, parameter types, and parameter values. Call stack information is shown only when the program being debugged is in a break state.
The call stack represents the various contexts that the XSLT execution is going through. For example, if there is a call from template "a" to template "b", template "a" and template "b" appear in the call stack window with the current context at the very top of the list. The user is able to see the query that is currently executing.
If the templates do not have a name in the XSLT file, the names generated by the XSLT processor are used.
Clicking an item other than the one at the top of the list indicates to the viewer where the XSLT execution branch happened using the standard green highlighting and green arrows.
The QuickWatch dialog box is used to evaluate XPath 1.0 expressions. The context node (the
self::node() node from the Locals window) provides the context for the execution of the XPath expression. The result of executing the XPath expression is displayed in the Watch window.
The following list describes some restrictions on the XPath expression evaluation.
Only built-in XPath functions are allowed.
Built-in XSLT functions such as
key(), and so on, are not allowed.
User-defined functions are not allowed.
For more information, see How to: Evaluate an XPath Expression.
The Disassembly window shows the assembly code that is generated by the XSLT compiler. This window can be used in the same manner as all other Visual Studio disassembly windows.
For more information, How to: Use the Disassembly Window.