WCF Service - sequence in XSD Complex Type definitions

[wurzel]

Anyway of stopping the .Net framework from imposing a sequence restriction on complex types?

We have a client who accesses our service via a handrolled SOAP message & every time we add a new field we get errors because they are not passing it in the correct position. (They should look at the WSDL but they just don't understand the concept. They don't even understand XML)

I don't see why sequence is important. Normally you can deserialise a known type from XML regardless of the order in which the elements appear.

[DimPrawn]

Change the XSD sequence to a choice

<xsd:choice minOccurs="0" maxOccurs="unbounded">
      <xsd:element name="Folder" type="folderType" />
      <xsd:element name="Bookmark" type="bookmarkType"/>
    </xsd:choice>

[wurzel]

Change the XSD sequence to a choice

<xsd:choice minOccurs="0" maxOccurs="unbounded">
      <xsd:element name="Folder" type="folderType" />
      <xsd:element name="Bookmark" type="bookmarkType"/>
    </xsd:choice>

Just wondering if it were possible to get the framework to do this rather than having to do it manually

[DimPrawn]

Just wondering if it were possible to get the framework to do this rather than having to do it manually

Not that I know of. Change the WSDL and regenerate the C#.