Is there a way to avoid the XmlSerializer to not initialize a null property when deserializing?

喜你入骨 提交于 2019-11-29 04:01:27

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.

Don't use Auto-Implemented Properties if you need a null there. use e.g.

public class MySerializableClass 
{ 
    List<MyObject> myList 
    public List<MyObject> MyList { get {return myList;} set {myList = value;} } 
} 

I had the same problem but adding the XmlArrayAttribute to the property with nothing set made it work for me

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

If you add a property with the name *PropertyName*Specified as a boolean the XmlSerializer will render the tag for the list only when it is true.

Example:

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

    [XmlIgnore]
    public bool MyListSpecified { get; set; }
}
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!