Timeline for Simple repository for a small/medium sized ASP.NET MVC site
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 10, 2016 at 1:29 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 10, 2016 at 1:29 | answer | added | RubberDuck | timeline score: 2 | |
| Nov 9, 2016 at 23:44 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 69 characters in body; edited tags; edited title
|
| May 23, 2016 at 15:11 | comment | added | BCdotWEB | That answer also explains to "go with a service pattern, where you construct an API that your application can use without knowing or caring whether the data is coming from Entity Framework, NHibernate, or a Web API". | |
| May 23, 2016 at 14:37 | comment | added | Mathias Hove | i am fully aware of entity framework having a built in repo. But having EF logic scattered across controllers can lead to a fully fledged maintenance hell. :) | |
| May 23, 2016 at 8:47 | comment | added | BCdotWEB | "The single best reason to not use the repository pattern with Entity Framework? Entity Framework already implements a repository pattern." | |
| May 23, 2016 at 8:46 | history | edited | BCdotWEB | CC BY-SA 3.0 |
deleted 68 characters in body
|
| May 23, 2016 at 6:27 | review | First posts | |||
| May 23, 2016 at 10:11 | |||||
| May 23, 2016 at 6:26 | history | asked | Mathias Hove | CC BY-SA 3.0 |