Visual Studio: generating code upon xsd problems with integers

Question

Can anyone tell me, why integer elements in xsd are being converted in String fields?

<xs:element name="OwnerID" type="xs:integer"/>

into

[System.Xml.Serialization.XmlElementAttribute(DataType = "integer")]
public string OwnerID
{
    get
    {
        return this.ownerIDField;
    }
    set
    {
        this.ownerIDField = value;
    }
}

my first assumption that all fields are strings attributed by real datatype was not right - dates are interpretered as dates, bools as bools - what's wrong with integer?

Thanks in advance!

score 4 · Accepted Answer · answered Nov 03 '11 at 08:05

4

You need something like this:

<xs:element name="OwnerID" >
    <xs:simpleType>
        <xs:restriction base="xs:int" />
    </xs:simpleType>
</xs:element>

answered Nov 03 '11 at 08:05

sq33G

3,320
1
23
38

We've got the solution almost simultaneously -) – Andrey Khataev Nov 03 '11 at 08:16
It's sufficient to just replace xs:integer with xs:int – isHuman May 11 '16 at 09:49

score 2 · Answer 2 · answered Nov 03 '11 at 11:09

2

sq33G's answer is correct, but I want to add that the reason your original XSD element

<xs:element name="OwnerID" type="xs:integer"/>

is converted to a string is because per W3C Numeric DataTypes, xs:interger represents any integer value. Since is not confined to a 32 or 64-bit number and there is no numeric data type in C# that can handle an unbounded integer, the Deserializer is choosing a string type since it is the only type that can safely handle this value.

answered Nov 03 '11 at 11:09

psubsee2003

8,563
8
61
79

I need to correct myself - i remembered the behavior incorrectly. xs:integer does map to the System.Decimal type – psubsee2003 Nov 06 '11 at 08:47

Visual Studio: generating code upon xsd problems with integers

2 Answers2