Serialization of Classes with modification in .net 2.0

Question

lets say I have this model

class Color
{
    string name;
    string type;
}

Class ColorsList
{
List<Color>;
}

and I need to populate those classes to xml

<ColorsList>
    <Color>red
        <type>brush</type>
    </Color>
    <Color>blue
        <type>spray</type>
    </Color>
</ColorsList>

I cant change my classes structure cause in that way I can bind it to a grid control.

what is the best practice for such a thing? is there a simple way to do that? I was thinking of creating a different model for the xml..

Your XML file looks wrong. The color names must appear as element or attribute values. — orel, Sep 23 '13 at 12:59
There are enough XML Attributes to control serialization to get both. — Ralf, Sep 23 '13 at 12:59
I don't think private fields are serializable. Not completely sure on this. — Rameez Ahmed Sayad, Sep 23 '13 at 13:02
Hi Ralf, can you give me some direction? and lets say all fields are public — Mushon, Sep 23 '13 at 13:02
Have a look at the XmlSerializer and serialize/deserialize methods http://msdn.microsoft.com/en-us/library/System.Xml.Serialization.XmlSerializer_methods.aspx — Philippe, Sep 23 '13 at 13:19

score 1 · Answer 1 · edited May 23 '17 at 12:11

Both XmlSerializer and DataContractSerializer can be used if the properties are public. They will create a larger and uglier XML than you described.

If you must serialize non public properties, you can still use DataContractSerializer (Can an internal setter of a property be serialized?).

Usage examples -

http://msdn.microsoft.com/en-us/library/bb675198.aspx

http://www.jonasjohn.de/snippets/csharp/xmlserializer-example.htm

2 Notes -

These serializers are slow - that should not be an issue if you save dozens or hundreds of them. If you plan to handle LOTS of these items - it might become an issue. You could use binary serializers (those in .net \ protobuf.net \ protosharp) or write your own XML serializers.
You presentation layer should not depend on the way you store your data and the opposite. If these two affect each other - your design may be too coupled.

UPDATE

Just noticed the .net 2.0 restriction. DataContractSerializer requires .net 3.0 and above.

score 0 · Answer 2 · answered Sep 23 '13 at 13:29

Strip the XmlWriterSettings and XmlSerializerNamespaces out of the example if thats not really relevant.

public class Color
{
    [XmlText]
    public string Name { get; set; }
    [XmlElement(ElementName = "type")]
    public string Type { get; set; }
}

class Program
{
    static void Main(string[] args)
    {
        List<Color> colorlist = new List<Color>();
        colorlist.Add(new Color() { Name = "red", Type = "brush" });
        colorlist.Add(new Color() { Name = "blue", Type = "spray" });

        XmlWriterSettings xws = new XmlWriterSettings();            
        xws.OmitXmlDeclaration = true;
        xws.Encoding = Encoding.UTF8;
        xws.Indent = true;

        XmlSerializerNamespaces ns = new XmlSerializerNamespaces();
        ns.Add("", "");

        StringBuilder output = new StringBuilder();
        using(var wr = XmlWriter.Create(output, xws))
        {
            XmlSerializer ser = new XmlSerializer(typeof(List<Color>), new XmlRootAttribute("ColorsList"));
            ser.Serialize(wr, colorlist, ns);
        }

        Console.WriteLine(output.ToString());
        Console.ReadLine();
    }
}

Serialization of Classes with modification in .net 2.0

2 Answers2