In my web method
, I get an object of some third party C# entity class. The entity class is nothing but the DataContract
. This entity class is quite com
I agree with @Werner Strydom's answer.
I decided to use the XmlSerializer
because code becomes maintainable and it offers performance I expect. Most important is that it gives me full control over the XML structure.
This is how I solved my problem:
I created entity classes (representing various types of Xml elements) as per my requirement and passed an instance of the root class (class representing root element) through XmlSerializer.
Small use of LINQ
in case of 1:M relationship:
Wherever I wanted same element (say Employee
) many times under specific node (say Department
) , I declared the property of type List
. e.g. public List
in the Department
class. In such cases XmlSerializer obviously added an element called Employees
(which is grouping of all Employee
elements) under the Department
node. In such cases, I used LINQ
(after XmlSerializer serialized the .NET object) to manipulate the XElement
(i.e. XML) generated by XmlSerializer. Using LINQ
, I simply put all Employee
nodes directly under Department
node and removed the Employees
node.
However, I got the expected performance by combination of xmlSerializer
and LINQ
.
Downside is that, all classes I created had to be public when they could very well be internal!
Why not DataContractSerializer
and LINQ-to-XML
?
DataContractSerializer
does not allow to use Xml attributes (unless I implement IXmlSerializable
). See the types supported by DataContractSerializer.LINQ-to-XML
(and IXmlSerializable
too) makes code clumsy while creating complex XML structure and that code would definitely make other developers scratch their heads while maintaining/changing it.Is there any other way?
XSD.exe
or tool like Xsd2Code and work directly with them if you are happy with the resulting classes.