Timeline for Unit of work + repository + service layer with dependency injection
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 1, 2015 at 21:53 | answer | added | Brad Firesheets | timeline score: 3 | |
| Sep 21, 2014 at 22:44 | history | edited | Jamal | CC BY-SA 3.0 | added 3 characters in body |
| Sep 21, 2014 at 0:20 | answer | added | Mathieu Guindon | timeline score: 7 | |
| Sep 20, 2014 at 23:55 | comment | added | Guillermo Gomez | Oh, I see... I wasn't aware of the Linq-to-SQL name conflict, thanks for bringing that up. I will modify it. | |
| Sep 20, 2014 at 23:51 | comment | added | Mathieu Guindon | Maybe it's just me, but DataContext clashes with the Linq-to-SQL context class in my mind (System.Data.Linq.DataContext). | |
| Sep 20, 2014 at 23:49 | comment | added | Guillermo Gomez | @Mat'sMug Yes, the DbContext implementation is the DataContext class. I updated the content of the question to include the DataContext code snippet. In your opinion, would it be better to rename it to a less confusing name? Do you have any suggestions for a new name? | |
| Sep 20, 2014 at 23:47 | history | edited | Guillermo Gomez | CC BY-SA 3.0 | added 877 characters in body |
| Sep 20, 2014 at 23:35 | comment | added | Mathieu Guindon | "The concrete implementation of the unit of work uses entity framework under the hood (DbContext)" - and yet you declare a DataContext - it's not very clear what's going on here, what version of EF are you using? Oh wait, have you called your DbContext implementation "DataContext"? | |
| Sep 20, 2014 at 23:04 | review | Close votes | |||
| Sep 21, 2014 at 12:26 | |||||
| Sep 20, 2014 at 23:03 | history | edited | Jamal | CC BY-SA 3.0 | deleted 22 characters in body; edited tags |
| Sep 20, 2014 at 22:23 | review | First posts | |||
| Sep 20, 2014 at 22:46 | |||||
| Sep 20, 2014 at 22:22 | history | asked | Guillermo Gomez | CC BY-SA 3.0 |