Steve Wellens


This Blog is dedicated to programming in the .Net enviroment

Serializing and Deserializing Objects…to and from…XML

Over on the Asp.Net forums I recently had the opportunity* to help a few lost souls by showing them how to serialize objects to XML and deserialize the XML back into objects. Since the question has come up more than once, I decided to BLOG it so I could refer similar questions in the future to this post.

*I use the word opportunity because by helping others I am forced to think hard about the technology and to think even harder about how to communicate the technology. It makes me better at what I do. All right then, enough after-school-special-feel-good-about-yourself-I'm-ok-you're-ok fluffy nonsense… on with the code:

Here is a simple class I'm going to work with. It has both properties and fields:

public class MyClass
{
    // old school property
    private int _Age;  
    public int Age  
    {
        get { return _Age; }
        set { _Age = value; }
    }
 
    // new school property
    public bool Citizen { get; set; }
 
    // there's nothing wrong with using fields
    public string Name;  
}

Here are the two functions to Serialize and Deserialize an object:

 
/// ---- SerializeAnObject -----------------------------
/// <summary>
/// Serializes an object to an XML string
/// </summary>
/// <param name="AnObject">The Object to serialize</param>
/// <returns>XML string</returns>
 
public static string SerializeAnObject(object AnObject)
{
    XmlDocument XmlDoc = new XmlDocument();
    XmlSerializer Xml_Serializer = new XmlSerializer(AnObject.GetType()); 
    MemoryStream MemStream = new MemoryStream();
    try
    { 
        Xml_Serializer.Serialize(MemStream, AnObject); 
        MemStream.Position = 0; 
        XmlDoc.Load(MemStream); 
        return XmlDoc.InnerXml; 
    }      
    finally 
    { 
        MemStream.Close(); 
    }
}
 
/// ---- DeSerializeAnObject ------------------------------
/// <summary>
/// DeSerialize an object
/// </summary>
/// <param name="XmlOfAnObject">The XML string</param>
/// <param name="ObjectType">The type of object</param>
/// <returns>A deserialized object...must be cast to correct type</returns>
 
public static Object DeSerializeAnObject(string XmlOfAnObject, Type ObjectType)
{       
    StringReader StrReader = new StringReader(XmlOfAnObject);
    XmlSerializer Xml_Serializer = new XmlSerializer(ObjectType);
    XmlTextReader XmlReader = new XmlTextReader(StrReader);
    try
    {
        Object AnObject = Xml_Serializer.Deserialize(XmlReader);
        return AnObject;
    }
    finally
    {
        XmlReader.Close();
        StrReader.Close();
    }
}

Here is some sample code showing how to use the functions.

Note: I keep these functions (and other functions) in a class I call MiscUtilities. You will have to modify the code…depending on where you place the functions.

protected void Button1_Click(object sender, EventArgs e)
{
    // create and initialize an object
    MyClass Test = new MyClass();
 
    Test.Age = 18;
    Test.Name = "Rocky Balboa";
    Test.Citizen = true;
 
    //  Serialize it
    String XML;
 
    XML = MiscUtilities.SerializeAnObject(Test);
 
    // Deserialize it
    MyClass Test2;
 
    Test2 = MiscUtilities.DeSerializeAnObject(XML, typeof(MyClass)) as MyClass;
 
    // TODO:  Get a cup of coffee and bask in the glory of rock solid code.
}

Here is what the XML string looks like (after formatting):

<?xml version="1.0"?>
<MyClass xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <Name>Rocky Balboa</Name>
  <Age>18</Age>
  <Citizen>true</Citizen>
</MyClass>

There are limitations: XmlSerializer does not serialize private fields, methods, indexers or read-only fields.

Once you have the XML string, you can email it, store it in a database, save it to disk, or…print a copy of it and have your mom tape it to the refrigerator next to the turkey picture you made in the second grade by tracing around your hand with a Crayola crayon.

I hope someone finds this useful.

Comments

Scott Allen said:

I think a generic parameter on deserialize would be nice, because the caller would not have to cast the return value, and you'd have a cleaner method signature. The type coercion would be hidden inside deserialize.

public static T DeSerialize<T>(string XmlOfAnObject)

{

   ...

   return (T)anObject;

   ...

}

Gives you:

var foo = Deserialize<Bar>(xml);

# July 2, 2009 12:57 PM

Dave said:

What if a field is added to the class after the xml file is created. Will it throw an error if its missing in the xml when you try to reconstitute it?

If it does throw the error will it say what field is missing?

# July 2, 2009 2:34 PM

SGWellens said:

If a field is added to the class, the reconstitution of an object from an old XML string will ignore the new field.  However, you can create a default constructor that initializes new fields to their desired defaults.  

This is much better than doing a binary serialization where you would need to write a conversion program each time a new version was issued.  

# July 2, 2009 4:07 PM

Jv said:

Why not use this instead: support.microsoft.com/.../815813 ? It's native .NET

# July 3, 2009 4:13 AM

flalar said:

You could also use generics for serialization

public static string Serialize<T>(T objectToSerialize, XmlSerializer serializer) where T : new()

       {

           StringBuilder stringBuilder = new StringBuilder();

           using (XmlWriter xmlWriter = XmlWriter.Create(stringBuilder))

           {

               serializer.Serialize(xmlWriter, objectToSerialize);

               xmlWriter.Flush();

           }

           return stringBuilder.ToString();

       }

# July 3, 2009 5:46 AM

DotNetShoutout said:

Thank you for submitting this cool story - Trackback from DotNetShoutout

# July 6, 2009 6:21 AM

sirdneo said:

I generally use extension methods to Serilize and De-Serlize objetcs to XML. Thanks for sharing

# September 9, 2009 2:43 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)