WCF message contract versioning

Question

0.00/5 (No votes)

See more:

Hi,
I had created a WCF service and used message contract to pass data to client.
I added a new member in message contract and I did not update the service reference of the client.
Now as per WCF versioning the old client should work,but In my case when I get the data after service call,some of the members are populated and some are null(members that are common between the old and new message contract).
I am also using transport='Streamed' for the service binding.

I would like to know whether I am missing something.

I faced the same issue with data contracts.

Thanks in advance.

Posted 24-Aug-15 0:18am

tkbineshb

Add a Solution

Comments

virusstorm 25-Aug-15 14:55pm

When you say "common", where any of them touched or changed in any way?

The documentation says "For service contracts, compatibility means new operations exposed by the service can be added but existing operations cannot be removed or changed semantically."
https://msdn.microsoft.com/en-us/library/ms731060(v=vs.110).aspx

tkbineshb 27-Aug-15 23:51pm

Hi,
I added a new member in the data contract response object.The service contract is the same.But when he response object is returned to the old client ,few members are populated and rest are null.If I update the service reference of the client,it works fine.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

tkbineshb · Accepted Answer · 2015-08-30T06:03:00

Solution 1

My problem is solved by adding 'Order' member of DataMember attribute with value =2 for newly added members

Posted 30-Aug-15 6:03am

tkbineshb

Updated 31-Aug-15 5:37am

v2