Data is lost when xml version tag is added to xml when posting to wcf

Question

Ok, i'm really lost on this one. I created a wcf service which i post xml to and the services does something with the data. Everything works just great except when i put the opening xml tag at the very top of my xml. the data comes through as null when i view everything in debug mode.

My C# code in the wcf is something like this:

public interface ITest
{
    [OperationContract]
    void DoWork();

    [OperationContract]
    [WebDispatchFormatter]
    [WebInvoke(UriTemplate = "MyTest", Method = "*")]
    void MyTest(PassedIn request);
}

[Serializable]
[DataContract(Namespace = "", Name = "")]
public class PassedIn
{
    public PassedIn() { }

    [DataMember]
    public string firstname {get; set;}
    [DataMember]
    public string lastname {get; set;}
    [DataMember]
    public string email {get; set;}
}

Here's the different xml posts:

<mypost>
    <firstname>test</firstname>
    <lastname>foo</lastname>
    <email>test@bar.com</email>
</mypost>

<?xml version="1.0"?>
<mypost>
    <firstname>test</firstname>
    <lastname>foo</lastname>
    <email>test@bar.com</email>
</mypost>

I was able to fix this where data isn't lost when the tag is in the xml by adding the order to the datamember like so:

public class PassedIn
{
    public PassedIn() { }

    [DataMember (order=1)]
    public string firstname {get; set;}
    [DataMember  (order=2)]
    public string lastname {get; set;}
    [DataMember  (order=3)]
    public string email {get; set;}
}

BUT now it has a reverse effect. If i don't have the "?xml version" tag the data comes through as null.

Has anyone run into this? Could really use some advice. Thanks

Don't know if this would matter, but have you tried decorating PassedIn with the `[DataContract]` attribute? — Tim, Jul 27 '12 at 19:24
ya i left that part out..its already in there. I just edited my code up there. — user1096865, Jul 27 '12 at 19:27
If you have control of both ends, have a look at [ServiceStack](http://servicestack.net/). — Chuck Savage, Jul 27 '12 at 23:57

score 1 · Accepted Answer · edited May 23 '17 at 11:55

i figured it out..when using the DataContractSerializer, order matters, but if you don't specify the order, by default the order is alphabetical which is why some data was getting set and others not.

I really didn't want order to matter, so i had to switch from DataContractSerializer to another serlization engine. XmlSerializer.

Links to some info that helped me: WCF Disable Deserialization Order Sensitivity http://msdn.microsoft.com/en-us/library/ms732038.aspx

Data is lost when xml version tag is added to xml when posting to wcf

1 Answers1