SAXONICA

Saxon Documentation
Full Contents
About Saxon
Changes in this Release
| Version 8.9 (2007-02-12)
| Version 8.8 (2006-09-05)
» | Version 8.7.3 (2006-06-13)
| Version 8.7.2 (2006-04-19)
| Version 8.7.1 (2006-04-13)
| Version 8.7 (2006-02-24)
| Version 8.6.1 (24 November 2005)
| Version 8.6 (3 November 2005)
| Version 8.5.1 (26 August 2005)
| Version 8.5 (2 August 2005)
| Version 8.4 (4 April 2005)
| Version 8.3 (11 February 2005)
| Version 8.2 (21 December 2004)
| Version 8.1.1 (8 October 2004)
| Version 8.1 (24 September 2004)
| Version 8.0 (1 June 2004)
Conditions of Use
Using XSLT 2.0
Using XQuery
Handling Source Documents
XML Schema Processing
XPath API for Java
Saxon on .NET
Extensibility
Saxon Extensions
Sample Saxon Applications
The Saxon SQL Extension
XSLT Elements
XPath 2.0 Expression Syntax
Function Library
Standards Conformance

# Changes on the .NET platform

Saxon is now explicitly supported on both .NET 1.1 and .NET 2.0 (previous releases were not validated on .NET 2.0, though experience showed that they ran without problems).

It is now possible to run queries and transformations directly on a DOM Document without first converting it to a Saxon tree. Instead of the `Build` method in the `DocumentBuilder`, use the new `Wrap` method. This creates a lightweight wrapper around the DOM document which makes it behave like the Saxon `NodeInfo` model. The code is very similar to the DOM wrapper used on the Java platform.

The `XdmValue` class is a wrapper for a Saxon `ValueRepresentation`. For applications that need more intimate access to the underlying Saxon objects, `XdmValue` now has `Wrap` and `Unwrap` methods that expose the underlying Java object.

The `SchemaManager` and `SchemaValidator` both now allow an `ErrorList` to be supplied, to capture error conditions encountered during schema compilation and instance document validation respectively.

Next