This question is locked. New answers and comments are not allowed.
I've taken a look at the n-tier application example code project. All in all, I don't like the idea of maintaining two disconnected sets of duplicated classes, one set in the persistent class data access layer and another in the business logic layer.
It's a total duplication of the same class definitions from a property perspective. And it also separates some logic away into yet another layer from the persistent classes. So if somehow code directly hits my persistent classes, the results will be different than code hitting the business layer classes. For example, if I build pre-commit validation into my classes, if I am using business layer that validation fire but it will not fire if the persisted classes are ever called directly.
After that long winded intro -
- What basic architecture approaches are you taking with OpenAccess?
- Are you putting extension functions directly into your persistent classes?
- Are you creating another kind of wrapper class to mask the persistent class in your web or windows applications? If so please link or give some detail.