About Entity Framework and NPersist

I read Mats Hellander’s post EF needs AOP today and I can only agree.

We have used the NPersist framework to provide Object-Relational Mapping in several projects and I really like the clean domain objects we can use. NPersist does not require that you mix you business logic with infrastructure code, implement interfaces or generate code. All thanks the use of Aspect oriented programming.

If you are not familiar with AOP, the short explanation is that when you need an instance of your domain class, the framework will on the fly create a sub-class of your class and add the needed code to get the infrastructure to work. This means less hand written code that is easier to read and maintain. Less code and more generated functionality also give less defects.