Timeline for Returning an IQueryable from an IRepository
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2015 at 14:22 | comment | added | Kristof Claes | There are other options like service classes or command and query classes. | |
| May 7, 2015 at 14:00 | comment | added | Mateusz | @Kristof Just a question to "Entity Framework are implementations of the Repository and the Unit of Work pattern". What I can to so people don't put new DbContext() in controller and complex logic in single method in MVC and then don't put also some logic in the views? I have legacy code where I cannot do any unit testing. To enable testing and prevent people from doing really bad code I need additional layer. Therfore I need to implement my own repositories for educational purposes. | |
| Nov 26, 2013 at 13:35 | history | edited | Kristof Claes | CC BY-SA 3.0 | The URL of Mark's blog post had changed. |
| Aug 28, 2012 at 12:08 | comment | added | Mihalis Bagos | Thanks for the reply. Seems that my concerns meet those of Seemann's many times, but I havent actually taken the time to read him, which I intend to. The only thing I disagree with is that a repository -even if strongly coupled- is very useful to encapsulate business logic, even if at a simpler access level (ie: VisibleItems, DeletedItems) etc, and help with DRY concept. | |
| Aug 27, 2012 at 11:37 | history | answered | Kristof Claes | CC BY-SA 3.0 |