Wcf difference faqs- 3
0 likes274 views
WCF Data Services and WCF RIA Services differ in their supported clients, data access layers, and development approaches. WCF Data Services supports a wider range of clients via REST and OData, while WCF RIA Services is tailored more for Silverlight. WCF Data Services supports Entity Framework by default and other data access layers with more effort, while WCF RIA Services directly supports Entity Framework, LINQ to SQL, and POCO models. Client development with WCF Data Services requires notifying the context for changes, while WCF RIA Services supports self-tracking entities and synchronized logic.
Wcf difference faqs- 3
- 1. 1.Difference between WCF Data Services and WCF RIA Services S.No WCF Data Services WCF RIA Services 1 Supported Clients: Supported Clients: Resource-based API, supports all Domain-based API, most tailored for clients via deep REST and OData use with Silverlight, but supports other support. clients via SOAP, JSON, and OData. 2 Supported Data Access Layers : Supported Data Access Layers : Targets EF. Other DALs are Supports EF, LINQ to SQL, and supported, but greater effort is POCO (custom persistence layer). required. 3 Client Development : Client Development : Requires you to notify the context Supports self-tracking entities, for change tracking. synchronized client/server logic, and much more (particularly with Silverlight). 4 Service Development : Service Development : Instant, code-less, extensible Requires you to code CRUD REST services out of the box operations manually in domain service (with EF); “free CRUD.” classes. Another good reference: http://silverlighttime.blogspot.in/2011/04/what-is-difference-between-wcf-data.html 2.Difference between Close and Abort in WCF Channels S.No Close Abort 1 Close performs graceful shutdown Abort shut downs Client channel of Client Channel immediately. 2 Close waits for in progress calls to Abort ends in progress calls. complete before closing 3 Close should not be called in Abort should be called in faulted faulted channels as it can throw channels. Communication or Timeout exception
- 2. 3.Difference between ASMX and SVC S.No ASMX SVC 1 Web service class inheritance for There is no Web service class ASMX is called WebService inheritance for SVC. 2 In ASMX,Web service class In SVC,Web service class attribute is attribute is called as called as ServiceContractAttribute. WebServiceAttribute. 3 In ASMX,Web service method In SVC,Web service method attribute attribute is called as is called as WebMethodAttribute. OperationContractAttribute. 4 In ASMX,Data class attribute is In SVC,Data class attribute is called as called as XmlRootAttribute DataContractAttribute. 5 In ASMX,Data class field In SVC,Data class field attribute is attribute is called as called as DataMemberAttribute. XmlElementAttribute 6 In ASMX,HTTP endpoint In SVC,HTTP endpoint resource is resource is called as .ASMX. called as .SVC 7 In ASMX, Serialization attribute In SVC, Serialization attribute is called is called as XMLSerializer as DataContractSerializer attribute. attribute. And, further updates on difference between questions and answers, please visit my blog @ http://onlydifferencefaqs.blogspot.in/