I\'m optimizing a custom object -> XML serialization utility, and it\'s all done and working and that\'s not the issue.
It worked by loading a file into an Xml
Another consideration is that XMLReader might be more robust for handling less-than-perfectly-formed XML. I recently created a client which consumed an XML stream, but the stream didn't have the special characters escaped correctly in URIs contained in some of the elements. XMLDocument and XPathDocument refused to load the XML at all, whereas using XMLReader I was able to extract the information I needed from the stream.