This article suggests splitting a WCF service solution into 2 projects, 1 for the contracts assembly and 1 for the implementation assembly.
Why is this advantageous? What do I stand to gain from this split? Thanks.
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.
The obvious advantage is you can share service contract dll file to your client. When you share a common service contract dll between the client and the server, your client can use the service with the
ChannelFactoryclass.(Two different ways WCF Service can be consumed by client. (Using ChannelFactory Vs. Proxies in WCF)