only for RuBoard |
When concepts are introduced in a sample section of code, we highlight the section to draw attention to the pertinent lines. Here's an example:
<?xml version="1.0" encoding="UTF-8" ?> <xsl:stylesheet version="1.1" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="/"> <table> <xsl:for-each select="links/link"> <tr> <td> <xsl:if test="position() mod 2 = 0"> <xsl:attribute name="bgcolor">silver</xsl:attribute> </xsl:if> <xsl:value-of select="@name" /> </td> </tr> </xsl:for-each> </table> </xsl:template> </xsl:stylesheet>
Much of the code in this book is also available for download from the web site. When the code is available, it is explicitly referenced in the text.
Sometimes, a bit of information is noteworthy, but might not fit directly within the text being discussed. In those cases, we use a sidebar.
Message Handlers and the xsl:message ElementFor the .NET base classes, the xsl:message element does not cause a trappable error. Instead, the message is output to the default message handler. For a Windows application project, the default handler is the output window. For a Console application, the default handler is the console window. For Web Forms applications, the message is suppressed. |
Generally, code is displayed using a monotype font. For example, the xsl:template element is discussed throughout the text, as is the XmlTextReader object.
If you have any comments on this book, I would love to hear from you. I am always looking for ways to improve this book and help make it one of the premier books on XML development with .NET.
only for RuBoard |