Direct dependancy on EF

Feb 27, 2014 at 12:53 PM
Out of curiosity why does the project "core" directly depend on entity framework assemblies?

Would it not be possible to have all the core interfaces and abstractions in a separate assembly and then move all the EF dependant classes to the EF6 assembly?

This should then make it easier to implement your code with nhibernate or some other orms. Also assemblies using the "core" repository would not directly depend on any EF and related assemblies.

Maybe there is some constraint that is preventing this re-factoring?
Feb 27, 2014 at 3:14 PM
Hi ktersius,

The latest release was to move towards separating all things that are EF into Repository.Pattern.Ef6, prior to this release everything was in one project/assembly, we are planning that the next release all things EF will completely be in Repository.Pattern.Ef6 including Repository.cs which is the only class now that depends on EF.
Marked as answer by lelong37 on 3/31/2014 at 10:36 PM