Is DataContract attributes required for WCF
I'm writing WCF service and his client. I want to send/receive objects of my custom classes, between service and client.
I have 3 modules
- WCF service
- WCF client
- common class library
Both WCF service and client have references to common class library. I don't want to mark all my class with DataContract attributes.
So, my question "Is DataContract attributes required for WCF?"
I use .NET 4 and netTcpBinding.
If I recall correctly(IIRC), if you don't use formal data-contract markers, it defaults to acting like a field-serializer. This will work, but is less easy to version, since private changes can break the client/server. IMO you should always formally decorate WCF types with the data-contract/data-member attributes. It will work without them, but for the wrong reasons (IIRC, originally it didn't work without formal markers).
"Is DataContract attributes required for WCF"
Technically, no. This is dependent on whether you use the DataContractSerializer or not (which is the default on many bindings).
There are other options:
- Consider alternative serializers
- Try using Data Contract Surrogates (attributes are still required somewhere, but it does potentially mean u can leave your class untouched, if thats relevant)
- Rely on the serialization defaults for when you serialize classes without Data Contract attributes
You can use several serializaton techniques with WCF, it's one of the nice adaptable things about it. Have a look:
It's not required to use DataContract attributes, your service will work just fine without them.
Having said that, I really don't think having your service and client share a class library is the best design approach. It would be a lot clearer if you'd expose your types through DataContracts.
What would happen when someday, someone wants to consume your service but don't have access to the shared class library?