Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using the .NET 4.0 Framework. I need to write some XML to interact with a web service. The parameters passed to the web service will be entered by an end-user.
My question is, what is the recommended approach for interacting with XML these days? It seems with every version of the .NET Framework there is a new way to do the same thing. But that doesn’t necessarily mean that it is the best. What does the community recommend in this case?
There isn’t a new one in every version. There are only two. It is unfortunate that there should be two, but there certainly aren’t more than two.
The one I recommend is
System.Xml.Linq.XDocumentand its associated classes. They provide a clean, useful API which allows you to use LINQ and the Enumerable extension methods. Generating an XML tree in this API is easy because you can nest constructor calls and you end up with code that looks very much like the XML itself.The one I don’t recommend is
System.Xml.XmlDocument. It is old, and it was designed to follow the W3C recommendations for an XML API. Consequently, it has no support for any modern or C#-specific ideas, including enumerables and LINQ. Generating an XML tree in this API is tortuous: you have to create each element individually and call methods likeAppendChildto turn them into a tree.