Comments on: Introduction to XML Serialization

By: Eamon

Eamon — Thu, 20 May 2010 04:26:22 +0000

Thank you for sharing your response, and offering some solutions.,lucy

By: AndrewS

AndrewS — Mon, 22 Jun 2009 01:42:35 +0000

You could reduce the line count a little like this and retain the same logic:

public static void Serialize(string filename, T data)
{
using ( TextWriter writer = new StreamWriter(filename) )
{
new XmlSerializer(typeof(T)).Serialize(writer, data);
}
}

public static T Deserialize(string filename)
{
using ( TextReader reader = new StreamReader(filename) )
{
return (T)new XmlSerializer(typeof(T)).Deserialize(reader);
}
}

By: C# Serializing Nullable Types by JohnnyCoder

C# Serializing Nullable Types by JohnnyCoder — Mon, 09 Jun 2008 19:56:06 +0000

[...] Introduction to XML Serialization [...]

By: Raghu

Raghu — Thu, 05 Jun 2008 01:25:54 +0000

Hi, I have a similar requirement to serialize a Business object into XML and I thought of using the XmlSerializer as well. But after a bit of experimentation i realized that there is no way to serialize properties that are read-only and the only workaround i could find was to have an empty set accessor for these props. Another particular type that i had problem with was TimeSpan. The XmlSerializer had no idea of how to serialize a TimeSpan type. So that means all my classes that have a Timespan prop have to inherit from IXmlSerializable and they must implement the WriteXml function of this interface. Did anyone else ever had a similar situation ? Please let me know.

Thanks in anticipation.

By: Mytymyky

Mytymyky — Tue, 20 May 2008 20:59:59 +0000

I came across this page looking for a solution to the problem i’m having and mentioned by Rob. Seems nullable types won’t serialize as attributes, only as elements. I use ALOT of nullable types in my apps (not sure its the best way to go, but oh well) and I was trying to add them ás attributes instead of elements (to eliminate part of the tag’s overhead) but I’ve had no luck.

For now element’s is how it will be…