Hi Dilip, You need to have a basic architecture in place. Presentation |Service layer|Business Layer|Data Access Layer | Database. Depending on the complexity of the project you may choose to merge layers in there, but its preferable to basically keep it loosely coupled like that. You need to break down your database schema into entities (business and/or data contracts) and use them as state-objects to pass them to presentation or whoever requires it. You should check viability of ADO.net entity framework- http://channel9.msdn.com/shows/Going+Deep/ADONET-Entity-Framework-What-How-Why/ And you can use the above entities from ADO.net entity framework as datacontracts in WCF, in fact they are marked with WCF data contract attribute anyways. In a SOA, dataset is discouraged because its not interoperable. But as far as you can see, if you don't need interoperability (Java or other technologies calling .net services). You should be fine to use DataSets as Data Contracts anyways. Thanks, -Phani
- Marked As Answer bySteven Cheng - MSFTMSFT, ModeratorThursday, September 24, 2009 3:03 AM
-
|