views:

526

answers:

1

I am using the new .NET 3.0 DataContractSerializer. I have both Nullable<> and List<> objects I am going to serialize. Example:

[DataContract(Namespace = "")]
class Test
{
    public static void Go()
    {
        Test test = new Test();

        var dcs = new DataContractSerializer(typeof(Test));
        dcs.WriteObject(new StreamWriter("test.xml").BaseStream, test);
    }

    [DataMember]
    public Nullable<int> NullableNumber = null;

    [DataMember]
    public int Number = 5;

    [DataMember]
    public List<int> Numbers = new List<int>();
}

When .NET serializes a null or an empty list, it puts in nil (for Nullable) and empty (for lists) elements into the XML. The above example generates:

<Test xmlns:i="http://www.w3.org/2001/XMLSchema-instance"&gt;
  <NullableNumber i:nil="true"/>
  <Number>5</Number>
  <Numbers xmlns:a="http://schemas.microsoft.com/2003/10/Serialization/Arrays"/&gt;
</Test>

For reasons I don't have time to describe I would like to eliminate the superfluous NullableNumber and Numbers elements, like so:

<Test xmlns:i="http://www.w3.org/2001/XMLSchema-instance"&gt;
  <Number>5</Number>
</Test>

Indeed, the above file deserializes with the serializer just fine.

Thanks for your help!

+4  A: 

Mark the field with

   [DataMember(EmitDefaultValue=false)]

That will work for at the least the nullable value type case. For the List case you may need to defer creation of the list until it is needed, or else null the member if it is empty before serialization.

Darren Clark