tag:blogger.com,1999:blog-11646261.post5836665361970236141..comments2024-01-02T00:43:44.344-08:00Comments on OakLeaf Systems: LINQ and Entity Framework Posts for 9/8/2008+Roger Jennings (--rj)http://www.blogger.com/profile/01700526164060680385noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11646261.post-87229712943112893132008-09-09T14:49:00.000-07:002008-09-09T14:49:00.000-07:00@AndyI asked the following question in a comment t...@Andy<BR/><BR/>I asked the following question in a comment to Jarek's post:<BR/><BR/>"Does Astoria consider the POCO Adapter's EFPocoContext a first-class data source, that is, supports IQueryable and induces the Astoria runtime to provide IUpdatable.<BR/><BR/>In other words, can it be plugged into an Astoria project without adding a significant amount of code?"<BR/><BR/>But haven't yet received Roger Jennings (--rj)https://www.blogger.com/profile/01700526164060680385noreply@blogger.comtag:blogger.com,1999:blog-11646261.post-7077840461961888822008-09-09T14:28:00.000-07:002008-09-09T14:28:00.000-07:00Thanks for pointing to the Persistence Ignorance (...Thanks for pointing to the Persistence Ignorance (POCO) Adapter for Entity Framework V1. I'd love your in depth thoughts on this, as to when it might be a viable (future proof) solution to use. And am also interested as to whether it works with ADO.NET Data Services and the rest of the Data Strategy elements.Anonymousnoreply@blogger.com