6

when I serialize a c# object with a nullable DateTime in it, is there a way to leave the null value out of the xml file instead of having 

 <EndDate d2p1:nil="true" xmlns:d2p1="http://www.w3.org/2001/XMLSchema-instance" />
James A Mohler
  • 11,060
  • 15
  • 46
  • 72
Patrick
  • 2,730
  • 4
  • 33
  • 55

3 Answers3

11

You can use the Specified extended property to leave out null values (or any other value, for that matter). Basically, create another property with the same name as the serialized property with the word Specified added to the end as a boolean. If the Specified property is true, then the property it is controlling is serialized. Otherwise, if it is false, the other property is left out of the xml file completely:

[XmlElement("EndDate")]
public DateTime? EndDate { get; set; }
[XmlIgnore]
public bool EndDateSpecified { get {
    return (EndDate != null && EndDate.HasValue); } }
mellamokb
  • 56,094
  • 12
  • 110
  • 136
0

I know this is an old thread, but in case someone else find this:

You can also implement a public method for each property to check whether it should be serialized or not. The convention is:

bool ShouldSerialize[YourPropertyName]();

For example, in your case

public bool ShouldSerializeEndDate(){
    return (EndDate != null && EndDate.HasValue);
}

Do this for each property you want to optionally serialize.

user1613569
  • 1
0

MSDN link

this allows you to say whether you want an empty element for null objects

iCollect.it Ltd
  • 92,391
  • 25
  • 181
  • 202
Pharabus
  • 6,081
  • 1
  • 26
  • 39
  • Actually this won't work because `DateTime` is a value type. From the documentation you linked: "**Additionally, you cannot set this property to false for nullable value types. When such types are a null reference (Nothing in Visual Basic), they will be serialized by setting xsi:nil to true.**" – mellamokb Oct 03 '11 at 15:17
  • good point, I did miss the fact he was dealing with a DateTime, thansk for pointing this out – Pharabus Oct 03 '11 at 15:36