1

Topic: DataContract-deserializatsija And the order of fields

All greetings! Whether there is a method to avoid deserialising errors if the order of elements in input XML does not coincide with the expected? For example: <Auth> <ApiLogin> asasd <ApiLogin> <ApiPassword> 456465 <ApiPasword> </Auth> works and <Auth> <ApiPassword> 456465 <ApiPasword> <ApiLogin> asasd <ApiLogin> </Auth> there is no class on the server [DataContract] internal class AuthInfo {///<summary>///The api login///</summary> [DataMember (IsRequired = true)] internal string ApiLogin;///<summary>///The api password///</summary> [DataMember (IsRequired = true)] internal string ApiPassword;} What for this check in sequence generally is necessary? Same does not mean that titles of elements in XML can be any PS. On the client in a class generated from WSDL of the order of fields is not present (even if them explicitly to specify in an initial class)

2

Re: DataContract-deserializatsija And the order of fields

Hello, mDmitriy, you wrote: D> All greetings! Whether D> there is a method to avoid deserialising errors if the order of elements in input XML does not coincide with the expected?  only substitution . D> PS. On the client in a class generated from WSDL of the order of fields is not present (even if them explicitly to specify in an initial class) the Order in the circuit, in it xs:sequence should be. Also sm https://stackoverflow.com/a/1727704/318263

3

Re: DataContract-deserializatsija And the order of fields

Hello, Sinix, you wrote: S> Emnip only substitution . I.e., not standard DataContractSerializer? S> the Order in the circuit, in it xs:sequence should be. S> also sm https://stackoverflow.com/a/1727704/318263 ...