in the example I believe there is an error. In BestPracticesMasterPage, Default.aspx.cs, you have in Page_Load event,
Shouldn't this be
Also, I'm having serious doubts about using OpenAccess the way you do. I believe that those who are using ORM's need some abstraction when using them so that we will be able to easily replace the current ORM with another one. Using this same example, what would be your suggestion to allow for absolutely zero coupling with the domain model (Open Access generated Model). The example in this website
is exactly what I mean, and would love to see that implemented here with OpenAccess. Also, manually creating Assembler classes with the mapping from the Generated Domain Model classes to our own business object classes as I already saw, is absolutely insane if you have many tables and relations. If I have to make the mapping manually, what's the point of using an ORM? I'm not in any way criticizing OpenAccess, but just trying to get some discussion about this.
Once again, it would be great to see an example addressing this issues.
PS: I would also love to hear what you think about returning IQueryable<T> to the upper layers from an existing List of objects instead of a collection of objects like "TestingPersonList" or even the usual List<>.