xsd.exe vs. enumeration

[John Saunders]

Given a schema as follows:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="testEnum" type="TestEnumUse"/>
<xs:complexType name="TestEnumUse">
<xs:sequence>
<xs:element name="testEnum" type="TestEnumType"/>
</xs:sequence>
</xs:complexType>
<xs:simpleType name="TestEnumType">
<xs:restriction base="xs:integer">
<xs:enumeration value="1"/>
<xs:enumeration value="2"/>
<xs:enumeration value="3"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>

xsd /class testenums.xsd

produces:

//------------------------------------------------------------------------------
// <autogenerated>
// This code was generated by a tool.
// Runtime Version: 1.1.4322.2032
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </autogenerated>
//------------------------------------------------------------------------------

//
// This source code was auto-generated by xsd, Version=1.1.4322.2032.
//
using System.Xml.Serialization;
/// <remarks/>
[System.Xml.Serialization.XmlRootAttribute("testEnu m", Namespace="",
IsNullable=false)]
public class TestEnumUse {

/// <remarks/>
public TestEnumType testEnum;
}

/// <remarks/>
public enum TestEnumType {

/// <remarks/>
[System.Xml.Serialization.XmlEnumAttribute("1")]
Item1,

/// <remarks/>
[System.Xml.Serialization.XmlEnumAttribute("2")]
Item2,

/// <remarks/>
[System.Xml.Serialization.XmlEnumAttribute("3")]
Item3,
}

Is there anything I can do, short of rewriting the generated code, to make
xsd.exe use "int" instead of an enum? I'd expect a similar problem with:

<xs:simpleType name="TestStringEnum">
<xs:restriction base="xs:token">
<xs:enumeration value="not a valid c# name"/>
<xs:enumeration value="this isn't, either"/>
</xs:restriction>
</xs:simpleType>

John