398 votes13 comments · [Closed] WCF Data Services Feature Suggestions · Flag idea as inappropriate… · Admin →
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. :)
1,081 votes14 comments · [Closed] WCF Data Services Feature Suggestions · Flag idea as inappropriate… · Admin →
Good news: this is coming – and not just on entity types but on complex types as well. Enums are part of the OData v4 protocol. In fact, it was one of the things we argued vociferously for precisely because of the number of votes on this issue.
Is it fixed yet?
Any update on this? :)