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.
Possible Duplicate:
Ambiguous reference in WCF and client application
I am using few classes from an assembly ‘X’ in my WCF whereas my client code uses same assembly to refer other set of classes.
This makes it necessary keep reference of assembly ‘X’ in client application.
which is causing the conflict as the proxy that I get on the client side has keeps the classes from assembly ‘X’ under different namespace.
Please suggest any solution.
Don’t use a pre-generated proxy. If you are sharing assemblies between your service and consumer code anyway then just also share the WCF contracts assembly and then use
ChannelFactoryto create a proxy when you need it.