Discovered that my request class (i.e. data contract) is not being declarated correctly upon being serialized. The working request message looks something like this: <SetDate xmlns='http://company.com/ns/2010/05/'> <request xmlns:a='http://company.com/ns/2010/05/' xmlns:i='http://www.w3.org/2001/XMLSchema-instance'> <a:ID i:nil='true'></a:ID> <a:IndexId>0</a:IndexId> <a:UserName i:nil='true'></a:UserName> <a:CreatedBy i:nil='true'></a:CreatedBy> </request> </SetDate> The data contract that does not work is: <SetDate xmlns='http://company.com/ns/2010/05/'> <request xmlns:i='http://www.w3.org/2001/XMLSchema-instance'> <ID i:nil='true'> </ID> <IndexId>0</IndexId> <UserName i:nil='true'></UserName> <CreatedBy i:nil='true'></CreatedBy> </request> </SetDate> Why would the serialization be so different? First request is serialized using a web reference - request class being used is apart of the web reference. The second, was found by executing the service from a proxy class (ie. creating a channel - etc) and instantiating a request class (data contract). Trying to figure out why my declarations are different. Any suggestions are greating appreciated.
var
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)