I do not see any reason for the Repository pattern to not work with Entity Framework.because Repository pattern is an abstraction layer we put on
our data access layer. Our data access layer can be anything from pure ADO.NET
stored procedures to Entity Framework or an XML file. In large systems, where we have data coming from different sources
(database/XML/web service), it is good to have an abstraction layer. I do
not believe that Entity Framework is enough abstraction to hide what goes on
behind the scenes. For more details: Click Here
We use cookies to ensure you have the best browsing experience on our website. By using our site, you
acknowledge that you have read and understood our
Cookie Policy &
Privacy Policy.
Hi Simond,
I do not see any reason for the Repository pattern to not work with Entity Framework.because Repository pattern is an abstraction layer we put on our data access layer. Our data access layer can be anything from pure ADO.NET stored procedures to Entity Framework or an XML file.
In large systems, where we have data coming from different sources (database/XML/web service), it is good to have an abstraction layer. I do not believe that Entity Framework is enough abstraction to hide what goes on behind the scenes.
For more details: Click Here