Who This Book Is For
| only for RuBoard |
Who This Book Is For
This book is written for ASP developers who want to learn about XML in the .NET Framework and its application to ASP solutions. We make the assumption that you have created HTML pages and are familiar with server-side and client-side programming. We assume that you have at least a passing
| only for RuBoard |
| only for RuBoard |
Who This Book Is Not For
While covering so many areas of XML, this book can not serve all audiences. If you are not familiar with ASP development, we suggest that you first read New Riders Publishing's
Inside ASP.NET
(2002). You might also find that your appetite for XSLT and XML has been whet: For a further discussion on XML and XSLT that introduces
| only for RuBoard |
| only for RuBoard |
The Level of This Book
This book is written at several different levels, from beginning to advanced. This is largely due to the nature of XML itself: Some topics can seem self-explanatory but warrant discussion, while others seem complex and obscure. The examples are written with both Visual Basic and C# developers in mind. Examples usually appear in one language or the other unless certain concepts
Because this book focuses on using XML with .NET, it assumes
| only for RuBoard |
| only for RuBoard |
Conventions Used in This Book
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
| only for RuBoard |