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.
In my client, I’m trying to declare an entity type from the service….
MyService.MyClass myClass = new MyService.MyClass();
....
MyClass isn’t available.
The assembly MyClass is within is referenced by MyService. What am I missing?
Generally, to preserve the service boundary, you work with mex-generated proxy classes at the client; these are structure only, so don’t have any methods etc (just properties), and may even have different names (and almost certainly a different namespace).
However; if this .NET to .NET, you can get WCF (via either svcutil or the IDE) to re-use types in existing assemblies. Via the IDE it does this automatically (by default – you can disable it) if you have a reference to a dll containing matching types. At the command line, you use
/rIIRC.