WCF Data Service - iOS oData SDK Issues?

In answer to my own question, I fixed the code simply by modifying the below, I add here in case anyone else has the same issue WebGet(ResponseFormat = WebMessageFormat. Json) public static void InitializeService(DataServiceConfiguration config) { config. SetEntitySetAccessRule("*", EntitySetRights.

All); config. SetServiceOperationAccessRule("*", ServiceOperationRights. All); config.

DataServiceBehavior. MaxProtocolVersion = DataServiceProtocolVersion. V2; }.

In answer to my own question, I fixed the code simply by modifying the below, I add here in case anyone else has the same issue. WebGet(ResponseFormat = WebMessageFormat. Json) public static void InitializeService(DataServiceConfiguration config) { config.

SetEntitySetAccessRule("*", EntitySetRights. All); config. SetServiceOperationAccessRule("*", ServiceOperationRights.

All); config. DataServiceBehavior. MaxProtocolVersion = DataServiceProtocolVersion.

V2; }.

I have a strange problem relating to a C# WCF Data Service, and a iOS client (using the oData SDK). However the connection simply hangs after I get a 200 status code (there are only 5 items in the database, so I know it is not an issue with the size of the data). I get results as expected.

I am at a loss as to what the missing piece of my jigsaw is, so any pointers would be really helpful.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions