Question

I have this class:

public class MySerializableClass
{
    public List<MyObject> MyList { get; set; }
}

If MyList is null when MySerializableClass is serialized, I need to have it null when it’s deserialised too, but the XmlSerializer always initializes it when it deserialises my class.

Is there a way to avoid it initializing null properties?

MyList is not even recorded in the serialized file when it’s null. When I load it with null values, and save it again, MyList is not null anymore, it’s serialized as a List<> with 0 items, but not null.

Thanks.

More info:

An IsDeserializing property is not viable due to some code restrictions in the structure of the class

Answer 1

This looks like a bug…

Even if you try to mark the property as nullable, it doesn’t seem to work.

[XmlArray(IsNullable = true)]
public List<MyObject> MyList { get; set; }

It serializes the MyList property as follows :

<MyList xsi:nil="true" />

So the XML clearly indicates that the list is null, but after deserialization, it is still initialized to an empty list…

If you replace List<MyObject> with MyObject[], it works fine (even without IsNullable = true), but it’s probably not what you want…

You should probably report this on Connect.