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 am developing an OData server with an entity that contains OpenType properties. Two new client projects have started: one for iOS, using OData4ObjC, and the other uses the generated .Net libraries (via DataSvcUtil).
As far as I can tell — neither support OpenType properties. Is this true? Perhaps I’m missing something? Are there typical workarounds?
I don’t know about the iOS one, the .NET one supports some types of use cases for open properties. If on the client you know which open properties you’re going to access, you can add those to the generated classes manually (the generated classes are partial). The client will then treat them as any other property and it should work. (You might need to set the DataServiceContext.IgnoreMissingProperties=true, so that it doesn’t fail if the property is not present on some instance from the server).
But a full support for open properties (as in being able to dynamically read and write whatever the server sends) is not implemented in the .NET client. You could use ODataLib to consume and produce such payloads, but it’s not as easy to use (http://www.nuget.org/packages/Microsoft.Data.OData)