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.
I want to move WCF contracts interfaces to third DLL and start consuming them from clients when I am generating proxy by hand.
Do those interfaces in the DLL have to have the [ServiceContract] attribute when I consume them from the client to generate a proxy ?
Any idea what is the best naming for Dll that will have only contracts and the DTOs to share between client and the server.
It is very common practice to put WCF data and service contract to separate assembly. In my previous project we used naming like
Company.OurProject.Contracts.dll.I think that to generate proxy with reusing existing classes you should put your interfaces for service contracts (those marked with
[ServiceContractAttribute]) and corresponding data contracts to that assembly. I would avoid putting there actual implementation of the services.Here is another great answer on SO with more insight into what can be reused when “Reuse types in referenced assemblies” is selected: WCF Service Reference generates its own contract interface, won't reuse mine