Home/ Questions/Q 4330242
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T09:56:10+00:00

I am using XmlSerializer against an XSD.EXE generated class. XmlSerializer serializer = new XmlSerializer(obj.GetType());

  • 0

I am using XmlSerializer against an XSD.EXE generated class. 

XmlSerializer serializer = new XmlSerializer(obj.GetType());

Throws up

InvalidOperationException Unable to
generate a temporary class (result=1).
error CS0030: Cannot convert type
‘itemOrderItemsItem[]’ to
‘itemOrderItemsItem’ error CS0029:
Cannot implicitly convert type
‘itemOrderItemsItem’ to
‘itemOrderItemsItem[]’

The fix (labeled <!--fix...--> below) says to add some silly element to my schema, but this isn’t working. This fix is five years old. Is there a solution yet? 

              <xs:sequence>
              <xs:element name="item" minOccurs="0" maxOccurs="unbounded">
                <xs:complexType>
                  <xs:sequence>
                    <xs:element name="model" type="xs:string" minOccurs="0" />
                    <xs:element name="description" type="xs:string" minOccurs="0" />
                    <xs:element name="material" type="xs:string" minOccurs="0" />
                    <xs:element name="lot" type="xs:string" minOccurs="0" />
                    <xs:element name="serial" type="xs:string" minOccurs="0" />
                    <xs:element name="transferQty" type="xs:string" minOccurs="0" />
                    <xs:element name="shipQty" type="xs:string" minOccurs="0" />
                  </xs:sequence>
                </xs:complexType>
              </xs:element>     
            </xs:sequence>
       <xs:attribute name="tmp" type="xs:string" /><!--fix...-->
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you have XML of the form

     <items>
    <item>
      <model>10</model>
      <description>Torque wrench</description>
      <material>100</material>
      <lot>3</lot>
      <serial></serial>
      <transferQty>1</transferQty>
      <shipQty></shipQty>
    </item>
    <item>
           //...
    </item>
    <item>
           //...
    </item>
  </items>

    Xsd.exe will generate a xsd:

    <xs:element name="items" minOccurs="0" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="item" minOccurs="0" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="model" type="xs:string" minOccurs="0" />
                        <xs:element name="description" type="xs:string" minOccurs="0" />
                        <xs:element name="material" type="xs:string" minOccurs="0" />
                        <xs:element name="lot" type="xs:string" minOccurs="0" />
                        <xs:element name="serial" type="xs:string" minOccurs="0" />
                        <xs:element name="transferQty" type="xs:string" minOccurs="0" />
                        <xs:element name="shipQty" type="xs:string" minOccurs="0" />
                      </xs:sequence>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>

    Then

    xsd.exe “this.xsd” /c

    Generates a class with two dimensional arrays (items[][]). I only wanted a one dimensional array. I changed the first line:

    <xs:element name="items" minOccurs="0"><!--got rid of maxOccurs (which is what causes the issue)-->

    Now it works. Guess the serializer just barfs on two dimensional arrays. Luckily I dont need them.

    • 0