> In .net 1.1, I used XPathDocument for read-only access to XML (specifically
> transforms) because there were major performance differences between that
[quoted text clipped - 3 lines]
> XmlDocument. so is XPathDocument now a historical artefact or should we
> still be using it for best performance?
As far as I understand XPathDocument is certainly not a historical
artefact, rather it is still the best input for XSLT and XPath. If you
need to make changes then use XmlDocument. Or of course with .NET 3.5
look into LINQ to XML.

Signature
Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/