| Subject: To MessageContract or not? |
| Group: microsoft.public.windows.developer.winfx.indigo |
| Date: 2/17/2008 9:04:58 AM |
| From: "travislspencer@gmail.com" [Email Address Protection] |
Good Morning All, I attended a user group meeting the other day on WCF, and the speaker suggested that all operation contracts should receive and return types decorated with the MessageContract attribute. The primary reason that he gave for adopting this design was to aid in versioning. By creating message contracts for both the request and response, one could alter the message contract without having to change the service contract. This seems like good advice. Has anyone tried this and found that it wasn't a good idea? Does anyone have any good blog posts or articles that they can refer me to with more info? Also, suppose I have a number of services wich RPC-style operation contracts and want to change them to use typed messages instead. How would I alter them in a way that existing clients continue to work? -- Regards, Travis Spencer |
| Back |