Printable View
Hi all,
I am developing a WCF application and i can send simple DataContract classes without problems. But when i try to send a class having a different type of class as a field, i get CommunicationException. Class structure is like below;
And i also defined both ClassB and ClassC as DataContract. I don't know if i am doing something wrong. Any help would be appreciated.Code:[DataContract]
public class ClassA
{
[DataMember]
public ClassB myObject1;
[DataMember]
public ClassC myObject2;
}
what is the message and innerexception of the CommuncationException.
Sound like you did the correct thing, but without any more information about the exception, we can't help you
Thanks for the reply Danny,
The reason of the CommunicationException seems that WCF cannot serialize the class B and class C objects in class A. I made some search and found out that i should use Surrogates to resolve that problem to make those classes serializable. But it requires much work to do that since if i use Surrogates i need to create Surrogate classes for class A and B to make them known types for the WCF service. And i found another thing showing that we can use KnownType or ServiceKnownType attributes for those inner class objects but all examples about those attributes are implemented on base class objects such as using a base Person class for both Employee and Employer classes.
Is there any other way to manage that.
Thanks in advance
Quote:
Originally Posted by dannystommen
Following is a codesnippet from my own project, which works fine only using DataContract and DataMember attributes.
As you can see, it has the same syntax as your example. I don't use Surrogates or (Service)KnownType, and it works just fine.Code:[DataContract]
public class User {
[DataMember]
public int ID {
...
}
[DataMember]
public string Username {
...
}
[DataMember]
public UserRole UserRole {
...
}
}
[DataContract]
public class UserRole {
[DataMember]
public int ID {
...
}
[DataMember]
public string Description {
...
}
}
Can you please quote the CommuncationException (message and innerexception), instead of saying only what is causing it.Quote:
The reason of the CommunicationException seems that WCF cannot serialize the class B and class C objects in class A