In Following post I am going show you how easily you can convert you object in the XML string, because sometime there is need of pass object and XML from one function to another and also convert XML string back to object. But As title suggest here I just going to discuss the conversion of object to XML string.
Following two way to achieve this task of converting Object to XML.
Before we start Below is class structure which object need to be convert in XML string.
Way 1 : Linq To XML
Output
Way 2 : Make use of XmlSerializer
You can easily convert the object in XML string by using Serializer as shown below. This process called as object serialization.
Output
Comparison between both the ways
For XmlSerializer you need to put attribute called [Obsolete] on top of property.
You can use one of the way as per your need. But if you just want to generate XML than its better to go for Linq to XML and if there is serialization/ de-serialization required than go for XmlSerializer .
Provide comments if you find more difference and there is thing change require in above. Thanks for reading.
Following two way to achieve this task of converting Object to XML.
Before we start Below is class structure which object need to be convert in XML string.
public class Product { public string Name { get; set; } public int Code { get; set; } public List<productType> types {get; set;} } public class productType { public string type {get; set;} }As you can see in structure Product is class and it's having list of producttype in it.
Way 1 : Linq To XML
List<productType> typ = new List<productType>(); typ.Add((new productType() { type="Type1"})); typ.Add((new productType() { type = "Type2" })); typ.Add((new productType() { type = "Type3" })); Product[] products = { new Product { Name = "apple", Code = 9,types=typ }, new Product { Name = "orange", Code = 4,types=typ }, new Product { Name = "apple", Code = 9 ,types=typ}, new Product { Name = "lemon", Code = 9,types=typ } };Above code is creating array of product which contains the object of product. Over all its initializing the product array object.Now to convert this in the XML using Linq following is code
XElement _customers = new XElement("Products", from c in products orderby c.Code select new XElement("product", new XElement("Code", c.Code), new XElement("Name", c.Name), new XElement("Types", (from x in c.types orderby x.type//descending select new XElement("Type",x.type)) )) ); Console.WriteLine(_customers.ToString());As you see in above code its converting the each property of object in XMLElement by using method of Linq To XML which is XElement. You can modify structure as per you needs here is more on Linq to XML
Output
Way 2 : Make use of XmlSerializer
You can easily convert the object in XML string by using Serializer as shown below. This process called as object serialization.
XmlSerializer xser = new XmlSerializer(products.GetType()); xser.Serialize(Console.Out, products); Console.ReadLine();As you see there just two line of code need to conversion. There is no need to write more amount of the code like Linq To XML, But if you want to control structure of the generated XML you need to decorate your class with XmlAttributes. Read more about this XmlSerializer
Output
Comparison between both the ways
- Big difference between both is way XML string is generated. That you can easily figure out form the Output of both the way.
- XmlSerializer provide more control on XML than than the Lin To XML.
- As stated with Linq to Xml you need to write down more amount of code to structure the XML string which is very easy with XmlSerializer. But if you dont want the default structure generated by XmlSerializer you need to use XmlAttributes for each property. with attribute class will be
public class Product { [XmlElement("Product Name")] public string Name { get; set; } [XmlElement("Code")] public int Code { get; set; } [XmlElement("Types")] public ListBut you can easily do this in Linq to XML.types {get; set;} }
- When you dont want to include some property in XML string. you just need to skip that property like this.
XElement _customers = new XElement("Products", from c in products orderby c.Code //descending select new XElement("product", //new XElement("Code", c.Code), new XElement("Name", c.Name), new XElement("Types", (from x in c.types orderby x.type//descending select new XElement("Type",x.type)) )) );in linq to xml you just need to remove it here i just commented Code so there is no element for Code.
For XmlSerializer you need to put attribute called [Obsolete] on top of property.
public string Name { get; set; } [Obsolete] public int Code { get; set; } public Listtypes {get; set;}
- Another Difference is Linq TO XML is faster than XmlSerializer which you can easy see by running the code its because XmlSerializer is Serializing object which might be using reflection and other metadata information about the object.
You can use one of the way as per your need. But if you just want to generate XML than its better to go for Linq to XML and if there is serialization/ de-serialization required than go for XmlSerializer .
Provide comments if you find more difference and there is thing change require in above. Thanks for reading.
Late to the party, but you should use [XmlIgnore], not [Obsolete] to denote an XML property to ignore.
ReplyDelete[XmlIgnore] should be used to skip some field, not [Obsolete]. [Obsolete] is for intimating developers that the member (field, method,...) is going to retire (ie. do not use)
ReplyDelete