class MyClass
{
// this is the nullable value container
private int? number;

// A regular integer property accessor.
// If the private nullable container is not
// defined, it will return the default value.
[XmlAttribute("number")]
public int Number
{
get { return number != null ? number.Value : default(int); }
set { this.number = value; }
}

// This boolean property uses the nullable container
// to check whether some value has been assigned
// XmlSerializer and Xsd.exe will use this adequately.
public bool NumberSpecified
{
get { return number != null; }
}
}

In this way you can have full nullable semantics. The public object interface still does not support ‘int?’, but the interaction is semantically equivalent, since you can simply ask whether ‘NumberSpecified’ is true to know if the value has been assigned or not.

Or if you really need a nullable property, you can just expose that with a [XmlIgnore] tag.

Best regards,

Gonçalo

///
/// Latitude.
///
[XmlAttribute]
public double Lat
{
get { return (double)lat; }
set { lat = value; }
}

public bool LatSpecified
{
get { return lat.HasValue; }
}