Which design pattern to use when using ORM?
Posted
by
RPK
on Programmers
See other posts from Programmers
or by RPK
Published on 2012-09-10T10:55:20Z
Indexed on
2012/09/10
15:49 UTC
Read the original article
Hit count: 473
I am writing a small ASP.NET Web Forms application. In my solution explorer, I added various class library projects to define layers, viz:
- Model
- Repository
- Presentation
- WebUI
Someone suggested me that this layered approach is not of much sense if I am using ORM tool like PetaPoco, which itself takes care of separation of data access layer.
I want to use PetaPoco micro-ORM and want to know which design pattern is suitable with ORM tools. Do I still need several class library projects to separate the concerns?
© Programmers or respective owner