New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is OData v4 supported? #32
Comments
OData v4 protocol is not fully supported, it's planned for Simple.OData.Client v.4 that will be based on Microsoft.OData.Core and will be available within next 3-4 months. But if you have examples of what doesn't properly work now, I can check it out. |
The problems seem to be deserializing the json result. For example, my service return this, a simple result using web api 2.2 and exception is throw (Im sorry but I dont have my demo at hand, I'll post the exception in a while): { Support for OData v4.0 in the future is great, but the problem I'm seeing is that web api 2.1 (which targets OData v3) supports Actions but no Fuctions, the Simple OData Client supports Fuctions but no Actions. Web Api 2.2 supports Actions and Fuctions, but seems to target only OData v4. I say "seems" because according to the documentation both versions are supported but it doesn´t says how to specify which versión to use (Im looking into this). I really like your client, but I need to solve how to use either functions or actions... Thanks Roygar |
I see. The problem is that current version of Simple.OData.Client only supports XML as result payload and Web API defaults to JSON. In principle the client should be able to request response as RSS XML, I will have to check what's going on. |
Ok, in the mean time I reverted to OData v3, I'll have to live without actions nor fuctions for the the moment.... thanks.. |
Any update on this and JSON serialization support? |
For you information: I have uploaded a 4.0.0-rc1 of Simple.OData.Client that supports OData V4 protocol and JSON payload. You can give it a try. |
I'd like to know if v4 of the odata protocol is supported. I tried to use a service created with the new Asp.net Web API 2.2 and I'm getting some problems.
The text was updated successfully, but these errors were encountered: