Don't abandon WCF Data Services
Dear OData team, I am requesting that you reconsider this:
Web API is not a drop in replacement for WCF Data Services.
We had to totally abandon OData because of this.
Web API OData does not support correct order of operations (for saving) nor transactions. (Among other things).
It also does not support DateTime (you must use DateTimeOffset for all your clients).
We moved to normal Web API. It can support OData syntax so I don't really see a reason to use the (extremely limited) Web API OData.
Michael DeMond commented
Man... pretty incredible to only find out about this now. I have put in over 18 months w/ WCF Data Services. It is pretty decent for when it works. Getting it there takes a lot of management, however. It is also a B-E-A-S-T with the amount of code involved to do something that at the end of the day is parsing URIs and JSON. I like that everything has been folded into WebAPI. I think that's the right move. I also think that WCF Data Services should be open-sourced to cater to those who love the product. I am sure they are out there. After my 18 months of exploring it, it has grown a little on me I have to admit. Open source is the way to go, MSFT. Embrace it and your community/users. :)
Adam Caviness commented
We are now fully invested in Web API OData and we love it. WCF Data Services was very good and the announcement wasn't graceful but overall the move to Web API was a very good move for us. The extensibility is everything we had hoped for and we are looking forward to vNext as well. Microsoft has my respect for all the work they put into Web API OData.
Tudor Turcu commented
Any update on this?
Nolan Venhola commented
The significant amount of time our team has to invest to reconfigure our entire client side code to swap out wcf data services for web api calls... is still minor compared to dealing with the bs of writing crud operations for each entity on the server side.
What a mess Microsoft.
Mauro Dalla Zuanna commented
As claimed in different sources WebApi should be a smaller and simpler subset of wcf for making services. Don't understand why they should have priority
Yannic Staudt commented
Like the others here, I (and my company) would really welcome further support of WCF Data Services, or at least an adequate replacement not requiring huge amount of rework in more complex situations (model first EF design, 100+ Tables).
Plus being stuck with a quite old EF release is starting to get annoying performance wise.
Adam Caviness commented
@Michael Pizzo, Is there any update to your team's consideration? As you may know, many teams are dependent on the former flagship implementation and Web API OData support doesn't yet offer a valid IEdmModel strategy to share between our database first strategy and an ODataConventionModelBuilder (try it yourself, former workarounds no longer work). Also, the Web API OData implementation doesn't yet offer transactional database updates! https://aspnetwebstack.codeplex.com/workitem/2011 I sincerely thank you for any update.
Fadi Barakat commented
There should always be an option for the client !
Any chance we can get an official word on whether Data Services will continue to be supported? Currently it is broken when used with Entity Framework 6 with regard to (at least) complex types not being able to be serialized.
Juliano Gonçalves commented
Can't agree more.
Being unable to update EF is already a burden, I can't imagine the problems later on when more features are added and bugs are fixed on EF and we just can't update it because WCF Data is stuck.
Michael Pizzo commented
Thanks for the feedback Adam. We will definitely consider this as we prioritize work between enhancing WCF Data Services and providing better support for new features in the WebAPI OData libraries.