Conclusion
The .NET XML DOM provides a consistent, well-defined interface for accessing XML data. It makes it quick and easy for folks raised on parsers such as MSXML and XML4J to get up and running with XML on the .NET platform. The downside of this approach is the DOM must build and keep its nodes in memory, consuming machine resources at an alarming rate for large documents. The next installment of this series will concentrate on the set of streaming interfaces to XML data in .NET Framework that focus on speed and performance while retaining ease of use.