Please consider the following Amount
value type property which is marked as a nullable XmlElement:
[XmlElement(IsNullable=true)]
public double? Amount { get ; set ; }
When a nullable
value type is set to null, the C# XmlSerializer result looks like the following:
<amount xsi:nil="true" />
Rather than emitting this element, I would like the XmlSerializer to suppress the element completely. Why? We're using Authorize.NET for online payments and Authorize.NET rejects the request if this null element exists.
The current solution/workaround is to not serialize the Amount
value type property at all. Instead we have created a complementary property, SerializableAmount, which is based on Amount and is serialized instead. Since SerializableAmount is of type String, which like reference
types are suppressed by the XmlSerializer if null by default, everything works great.
/// <summary>
/// Gets or sets the amount.
/// </summary>
[XmlIgnore]
public double? Amount { get; set; }
/// <summary>
/// Gets or sets the amount for serialization purposes only.
/// This had to be done because setting
value types to null
/// does not prevent them from being included when a class
/// is being serialized. When a nullable
value type is set
/// to null, such as with the Amount property, the result
/// looks like: >amount xsi:nil="true" /< which will
/// cause the Authorize.NET to reject the request. Strings
/// when set to null will be removed as they are a
/// reference type.
/// </summary>
[XmlElement("amount", IsNullable = false)]
public string SerializableAmount
{
get { return this.Amount == null ? null : this.Amount.ToString(); }
set { this.Amount = Convert.ToDouble(value); }
}
Of course, this is just a workaround. Is there a cleaner way to suppress null
value type elements from being emitted?
