I have a project to expose Entity Framework data via a web service. I am wondering should I use OData or write my own WCF services? It seems that OData is dead. Am I right?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a project to expose Entity Framework data via a web service. I am wondering should I use OData or write my own WCF services? It seems that OData is dead. Am I right?
The WCF Data Services team has just recently published a new WCF Data Services v5.1.0 (RC) release….
I don’t see any signs of a demise here, really…. read their team blog! They’ve even announced to be releasing more frequently in the future!
Doesn’t sound anything like dead to me…
Basically, OData / WCF Data Services is the fastest way to publish an Entity Framework data model to the web. If it’s good enough for you, if it covers all your needs – then by all means – USE IT!