views:

104

answers:

4

When set up an object for serialization I do the following:

[Serializable]
public class ContentModel
{
    public int ContentId { get; set; }
    public string HeaderRendered { get; set; }

    public ContentModel()
    {
        ContentId = 0;
        HeaderRendered = string.Empty;
    }

    public ContentModel(SerializationInfo info, StreamingContext ctxt) 
    {
        ContentId = (int)info.GetValue("ContentId", typeof(int));
        HeaderRendered = (string)info.GetValue("HeaderRendered", typeof(string));
    }

    public void GetObjectData(SerializationInfo info, StreamingContext context)
    {
        info.AddValue("ContentId ", ContentId);
        info.AddValue("HeaderRendered", HeaderRendered);
    }
}

It's quite exhausting when there are lots of properties. Is there a simpler or less verbose way of doing this in C# 4.0?

+2  A: 

Why are you doing this by hand? BinaryFormatter already knows how to do this automatically. If filtering the fields is important then make another class that just stores the ones that you want to serialize.

Hans Passant
+8  A: 

You don't need the extra constructor or the GetObjectData method unless you want to customize the serialization mechanism. If you have simple properties, the default serialization mechanism will handle them quite well. All you need is the Serializable attribute, and you're golden.

Nader Shirazie
A: 

I'd like to add that since your class doesn't implement ISerializable, your custom GetObjectData method may never be called.

Matthew Ferreira
+2  A: 

You could also consider using DataContract serialization which makes it easy to output JSON or XML if you ever need that.

Hightechrider
This. DataContract Serializers make vanilla-case serializations trivial.
JerKimball