XmlTextReader vs. XDocument

by

If you’re happy reading everything into memory, use XDocument. It’ll make your life much easier. LINQ to XML is a lovely API.

Use an XmlReader (such as XmlTextReader) if you need to handle huge XML files in a streaming fashion, basically. It’s a much more painful API, but it allows streaming (i.e. only dealing with data as you need it, so you can go through a huge document and only have a small amount in memory at a time).

There’s a hybrid approach, however – if you have a huge document made up of small elements, you can create an XElement from an XmlReader positioned at the start of the element, deal with the element using LINQ to XML, then move the XmlReader onto the next element and start again.

More Related Contents:

  1. Query an XDocument for elements by name at any depth
  2. What is the difference between Linq to XML Descendants and Elements
  3. how to use XPath with XDocument?
  4. get line number for XElement here
  5. Finding element in XDocument?
  6. How can I remove empty xmlns attribute from node created by XElement
  7. XDocument or XmlDocument
  8. Read XML Attribute using XmlDocument
  9. How would you compare two XML Documents?
  10. Why does C# XmlDocument.LoadXml(string) fail when an XML header is included?
  11. Format a date in XML via XSLT
  12. Escape invalid XML characters in C#
  13. Converting XDocument to XmlDocument and vice versa
  14. How to read attribute value from XmlNode in C#?
  15. Serialize a nullable int
  16. XmlSerializer – There was an error reflecting type
  17. How to serialize/deserialize simple classes to XML and back
  18. Fastest way to add new node to end of an xml?
  19. How to Get XML Node from XDocument
  20. How to write a comment to an XML file when using the XmlSerializer?
  21. XML file creation using XDocument in C#
  22. C# XDocument Load with multiple roots
  23. Parsing XML using XDocument
  24. How to prevent System.Xml.XmlException: Invalid character in the given encoding
  25. How to print using XDocument
  26. Linq to XML – update/alter the nodes of an XML Document
  27. Use the XmlInclude or SoapInclude attribute to specify types that are not known statically
  28. Data at the root level is invalid [duplicate]
  29. Force XDocument to write to String with UTF-8 encoding
  30. Reading XML with an “&” into C# XMLDocument Object

Leave a Comment