XSD Types Vs DataContract Types

Topics: General Discussion Forum, Service Factory Modeling Edition Forum
Feb 5, 2008 at 7:36 PM

In our operations we are using all Request and Response as XSD Messages. Thus all the data types are defined in the XSD schema. (Its all new development and no legacy application).
So there is no need to have DataContract Model in the solution. We have designed the ServiceContact and Host models.

Is this approach correct? Is there any reasoning for choosing between XSD Types Vs DataContract Types? Am I missing something here?

Thanks & Regards,
Feb 6, 2008 at 12:35 AM
The XSD Messages are typically intended for "Contract-First" scenarios like yours.
On the other hand, you may use DataContract types defined in your DC model that will let you model your contract elements in a graphical way (thought not as standard or interoperable way as a schema).
Both of them are fine but depends on your design needs or legacy constrains.