BTW - I think MS considers this an XSD.exe bug. It also affects the xs:positiveInteger, xs:nonNegativeInteger, and related cousins.
For that family of types, the work around is to use xs:int and then restrict the type with minInclusive, maxInclusive, etc. facets. >Instead of : >> <xs:element name="i" type="xs:integer"/> > >Use > > <xs:element name="i" type="xs:int"/> > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
