ADO.NET Data Service and non-public properties in Entity Data Model

2 Jul 2009 1 mins Entity Framework, OData/Data Services (Astoria)

I was punch directly to my face right now. Everytime I’m doing some ADO.NET Data Services (Astoria) speak I’m showing simple models, with almost no modifications. And everything works great. But I found, right now, that if you have entity in your model with property access getter or setter setted to anything except public, the service will not work. Grrr.

I understand that hiding setter causes the updates or inserts to stop working. But why the getter? If I limit my entity set to i.e. AllRead, then the querying should just work. Hmm, it’s probably related to missing select support (in 3.5SP1 as well as 4.0).

Anyway it was really “interesting” 😉 to find this out.

Jiří Činčura is .NET, C# and Firebird expert. He focuses on data and business layers, language constructs, parallelism, databases and performance. For almost two decades he contributes to open-source, i.e. FirebirdClient. He works as a senior software engineer for Microsoft. Frequent speaker and blogger at www.tabsoverspaces.com.