DataContract v/s DataType

Sep 10, 2007 at 11:17 PM
Edited Sep 11, 2007 at 9:28 AM

In WCF, "DataTypes" got renamed to "DataContract" (thats kinda the WCF way) but are there any difference?
In your words - what are the difference between a datacontract and a datatype? If any?

And would you consider a class - created as an ASMX standard DataType - filled with XmlSerializer declarations, namespaces etc, as a DataContract? I mean - it looks like a fair implementation of a DataContract (to me). Say you had to upgrade a Webservice to WCF - would it be correct to rename the DataType namespace to DataContracts? Even if the DataContractSerializer wasnt used?

In essence the question could be boiled down to a matter of namespace: Do I put "datatypes" that is NOT marked for serialization by the dataContractSerializer in the "something.DataContracts" namespace or in the "something.DataTypes" namespace. What would be best practice?

All thoughts appreciated...