The most efficient way to parse Xml

Question

The .Net framework now has (at least) four different methods of reading an Xml string. I\'ve used each of XmlDocument, XmlReader, XPath and XElement, but which is the most e

Answer 1

The three most common methods to read are:

XmlDocument It reads the whole file in a tree structure that can then be accessed using XPath or by browsing all the nodes. It requires a lot of memory for very large file since the whole XML structure must be loaded in memory. Very good and simple to use for smaller files (less then a few megs).

XmlReader Fast, but also a real pain to use since it's sequential. If you ever need to go back, you can't, and XML structure are usually very prone to having disorganised orders. Also, if you read from a non ending stream of XML, this is probably the only way to go.

XML serializers This basically does everything for you, you provide the root object of your model and it creates and read the XML for you. However, you have almost no control over the structure, and reading older versions of your object is a pain. So this won't work very well for persistance.

XDocument and LINQ to XML As Daniel Straight pointed out. But I don't know it enough to comment. I invite anyone to edit the post and add the missing info.

---

Now writing is another story. It's a pain to maintain a XmlDocument and XmlWriter is a breeze to use.

I'd say, from my experience, that the best combo is to write using XmlWriter and read using XmlDocument.