Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What are the pro / cons to having the client consume a WCF service either via adding a reference to the service (and basically everything is generated for you) or having the client implement a shared interface and them having to code class manually?
Thanks!
In general, if you don’t use code generation, then you’ll have to write by hand what would otherwise be generated for you.
The “maintenance issue” that Andrew mentions is solved by simply using “Update Service Reference” when the service contract changes. If this becomes a hassle, then create a separate project to contain all of the proxy classes. You then only need to use “Update Service Reference” in one place.
Of course, if the service contract or related contracts change in an incompatable manner, then your client code will have to change. That’s true regardless of which technique you use.