Question

我的解决办法包括两个项目:

a class library project (named as DataAccess) that defines a class (named as MyContext) inheriting from DbContext. As DbContext is defined in EntityFramework.dll assembly, I need to add a reference to this assembly into this class library project. I have no confusion in this mechanism.
a console application project (named as Tester) that consumes the DataAccess class defined in the class library above. Adding a reference to the assembly of the class library above is understandable. Unfortunately, I cannot compile the solution until I add a reference to EntityFramework.dll into this console application.

Why do we need to add a reference to an assembly, from which a class library project inherits, into a consumer project? In my mental model, it is enough to only add a reference to DataAccess project assembly into Tester project and the chained references should be done automatically.

Answer 1

由于<代码>MyContext中的许多行为从实体框架的基类中继承。如果您将这些方法(例如SaveChanges(>)从中删除, 试验就需参考该方法界定的类别图书馆。

如果你只能使用您的班级图书馆界定的<代码>MyContext,我认为你可以不提及基类。

Answer 2

Because otherwise EntityFramework.dll wont get copied to the output directory when you build your project and your library won t be able to access it.

如果你能够将<代码>EntityFramework.dll纳入你的图书馆(直线查询——和“财产”),那么你就不必提及你提出的假释申请。

友情链接