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 currently offer a service with many methods via WCF. I’d like to refactor so the single service is split into multiple classes, each offering a different set of functionality. However, I’d prefer to still have a single connection to the client. Is this possible?
I guess the answer is No, so how should I solve this issue? Is there a workaround? Or is my idea completely stupid and I should change the design of the application?
Remember E = ABC (Endpoint = Address, Binding, Contract). With a different contract, even with all else equal, you’ve still got a different endpoint.
However, a single service can implement multiple service contracts. This would allow a single .svc file to be the target of several different service contracts, all configured as URLs relative to the .svc.