将库从 ObjectContext 转换为 DbContext
我有一个库(基于旧博客文章中的代码),它允许我使用实体框架非常轻松地围绕我的数据访问包装外观。它使用 ObjectContext 并且对于我的目的来说表现得足够好。
但现在,我们首先使用 DbContext 兴奋地研究代码,当然希望尽可能多地重用/适应我们现有的工作。
一切都很顺利,天真地用 IObjectContextAdapter 转换我们的 Facade 支持库,直到我们尝试使用我们的 Facade,此时收到以下错误:
类型“Employee”不能用作泛型类型或方法“DbContextManagement.FacadeBase”中的类型参数“TEntity”。没有从“Employee”到“System.Data.Objects.DataClasses.EntityObject”的隐式引用转换
MSDN 说:
DbContext API 不支持 EntityObject 派生类型,要使用这些实体类型,您必须使用 ObjectContext API。
很好,但是我该如何继续完成重构以绕过这种无能呢?
下面是一些代码(引入了换行符):
FacadeBase.cs
namespace DbContextManagement
{
using System;
using System.Collections;
using System.Configuration;
using System.Data.Entity;
using System.Data.Entity.Infrastructure;
using System.Data.Metadata.Edm;
using System.Data.Objects.DataClasses;
using System.Linq;
using System.Reflection;
public abstract class FacadeBase<TDbContext, TEntity>
where TDbContext : DbContext, new()
where TEntity : EntityObject
{
protected TDbContext DbContext
{
get
{
if (DbContextManager == null)
{
this.InstantiateDbContextManager();
}
return DbContextManager.GetDbContext<TDbContext>();
}
}
private DbContextManager DbContextManager { get; set; }
public virtual void Add(TEntity newObject)
{
var context = ((IObjectContextAdapter)this.DbContext).ObjectContext;
string entitySetName;
if (newObject.EntityKey != null)
{
entitySetName = newObject.EntityKey.EntitySetName;
}
else
{
string entityTypeName = newObject.GetType().Name;
var container = context.MetadataWorkspace.GetEntityContainer(
context.DefaultContainerName,
DataSpace.CSpace);
entitySetName = (from meta in container.BaseEntitySets
where meta.ElementType.Name ==
entityTypeName
select meta.Name).First();
}
context.AddObject(entitySetName, newObject);
}
public virtual void Delete(TEntity obsoleteObject)
{
var context = ((IObjectContextAdapter)this.DbContext).ObjectContext;
context.DeleteObject(obsoleteObject);
}
private void InstantiateDbContextManager()
{
var objectContextManagerConfiguration =
ConfigurationManager.GetSection("DbContext") as Hashtable;
if (objectContextManagerConfiguration != null &&
objectContextManagerConfiguration.ContainsKey("managerType"))
{
var managerTypeName =
objectContextManagerConfiguration["managerType"] as string;
if (string.IsNullOrEmpty(managerTypeName))
{
throw new ConfigurationErrorsException(
"The managerType attribute is empty.");
}
managerTypeName = managerTypeName.Trim().ToLower();
try
{
var frameworkAssembly =
Assembly.GetAssembly(typeof(DbContextManager));
var managerType =
frameworkAssembly.GetType(managerTypeName, true, true);
this.DbContextManager =
Activator.CreateInstance(managerType) as DbContextManager;
}
catch (Exception e)
{
throw new ConfigurationErrorsException(
"The managerType specified in the
configuration is not valid.", e);
}
}
else
{
throw new ConfigurationErrorsException(
"A Facade.DbContext tag or its managerType attribute
is missing in the configuration.");
}
}
}
}
EmployeeFacade.cs
namespace Facade
{
using System.Collections.Generic;
using System.Linq;
using DataModel;
using DataModel.Entities;
using DbContextManagement;
public sealed class EmployeeFacade : FacadeBase<FleetContext, Employee>
{
public Employee GetById(int? employeeId)
{
return employeeId == null
? null
: this.DbContext.Employees.FirstOrDefault(m => m.Id == employeeId);
}
}
}
Employee.cs
namespace DataModel.Entities
{
public class Employee
{
public int Id { get; set; }
public string Surname { get; set; }
public string Forename { get; set; }
public string EmployeeNumber { get; set; }
}
}
I have a library (based on code found in an old blog post) that allows me to very easily wrap a façade around my data access using Entity Framework. It uses ObjectContext and has performed well enough for my purposes.
But now, we are excitedly investigating code first using DbContext and of course would like to reuse / adapt as much of our existing effort as possible.
Everything went ok naively converting our Facade enabling library with IObjectContextAdapter until we tried to utilise our facade, when the following error was received:
The type 'Employee' cannot be used as type parameter 'TEntity' in the generic type or method 'DbContextManagement.FacadeBase'. There is no implicit reference conversion from 'Employee' to 'System.Data.Objects.DataClasses.EntityObject'
MSDN says:
EntityObject derived types are not supported by the DbContext API, to use these entity types you must use the ObjectContext API.
That's fine, but how would I then go ahead completing my refactor to bypass this inability?
Here's some code (line breaks introduced):
FacadeBase.cs
namespace DbContextManagement
{
using System;
using System.Collections;
using System.Configuration;
using System.Data.Entity;
using System.Data.Entity.Infrastructure;
using System.Data.Metadata.Edm;
using System.Data.Objects.DataClasses;
using System.Linq;
using System.Reflection;
public abstract class FacadeBase<TDbContext, TEntity>
where TDbContext : DbContext, new()
where TEntity : EntityObject
{
protected TDbContext DbContext
{
get
{
if (DbContextManager == null)
{
this.InstantiateDbContextManager();
}
return DbContextManager.GetDbContext<TDbContext>();
}
}
private DbContextManager DbContextManager { get; set; }
public virtual void Add(TEntity newObject)
{
var context = ((IObjectContextAdapter)this.DbContext).ObjectContext;
string entitySetName;
if (newObject.EntityKey != null)
{
entitySetName = newObject.EntityKey.EntitySetName;
}
else
{
string entityTypeName = newObject.GetType().Name;
var container = context.MetadataWorkspace.GetEntityContainer(
context.DefaultContainerName,
DataSpace.CSpace);
entitySetName = (from meta in container.BaseEntitySets
where meta.ElementType.Name ==
entityTypeName
select meta.Name).First();
}
context.AddObject(entitySetName, newObject);
}
public virtual void Delete(TEntity obsoleteObject)
{
var context = ((IObjectContextAdapter)this.DbContext).ObjectContext;
context.DeleteObject(obsoleteObject);
}
private void InstantiateDbContextManager()
{
var objectContextManagerConfiguration =
ConfigurationManager.GetSection("DbContext") as Hashtable;
if (objectContextManagerConfiguration != null &&
objectContextManagerConfiguration.ContainsKey("managerType"))
{
var managerTypeName =
objectContextManagerConfiguration["managerType"] as string;
if (string.IsNullOrEmpty(managerTypeName))
{
throw new ConfigurationErrorsException(
"The managerType attribute is empty.");
}
managerTypeName = managerTypeName.Trim().ToLower();
try
{
var frameworkAssembly =
Assembly.GetAssembly(typeof(DbContextManager));
var managerType =
frameworkAssembly.GetType(managerTypeName, true, true);
this.DbContextManager =
Activator.CreateInstance(managerType) as DbContextManager;
}
catch (Exception e)
{
throw new ConfigurationErrorsException(
"The managerType specified in the
configuration is not valid.", e);
}
}
else
{
throw new ConfigurationErrorsException(
"A Facade.DbContext tag or its managerType attribute
is missing in the configuration.");
}
}
}
}
EmployeeFacade.cs
namespace Facade
{
using System.Collections.Generic;
using System.Linq;
using DataModel;
using DataModel.Entities;
using DbContextManagement;
public sealed class EmployeeFacade : FacadeBase<FleetContext, Employee>
{
public Employee GetById(int? employeeId)
{
return employeeId == null
? null
: this.DbContext.Employees.FirstOrDefault(m => m.Id == employeeId);
}
}
}
Employee.cs
namespace DataModel.Entities
{
public class Employee
{
public int Id { get; set; }
public string Surname { get; set; }
public string Forename { get; set; }
public string EmployeeNumber { get; set; }
}
}
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
如果您的实体派生自
EntityObject
,并且您想要重用的代码依赖于基于EntityObject
的实体,那么它就是一个阻碍。在您的实体是 POCO(无EntityObject
父级)之前,您无法使用 DbContext API。顺便提一句。您可以仅使用与
ObjectContext
(和 POCO)进行代码映射,而无需使用DbContext
。您只需要:EntityTypeConfiguration
或ComplexTypeConfiguration
的类DbModelBuilder
收集您的配置并调用Build
获取DbModel
实例DbModel
实例上调用Compile
获取DbCompiledModel
ObjectContext
实例时,请在编译模型上调用CreateObjectContext
请注意,代码映射的功能集更加有限,因此并不是您当前拥有的所有功能EDMX将可以通过代码映射来实现。
If your entities are derived from
EntityObject
and the code you want to reuse is dependent onEntityObject
based entities then it is a show stopper. You cannot use DbContext API until your entities are POCOs (noEntityObject
parent).Btw. you can use code only mapping with
ObjectContext
(and POCOs) without ever usingDbContext
. You just need to:EntityTypeConfiguration
orComplexTypeConfiguration
based class for each your POCO entity / complex type describing the mappingDbModelBuilder
to collect your configurations and callBuild
to getDbModel
instanceCompile
on yourDbModel
instance to getDbCompiledModel
ObjectContext
instance callCreateObjectContext
on compiled modelJust be aware that code mapping has much more limited feature set so not everything you currently have in EDMX will be possible to achieve through code mapping.
感谢上面给出的链接中原始代码的作者,这就是我最终得到的结果。它通过了基本场景,但我尚未尝试更深入的导航和相关查询。即使出现问题,我认为这也将是错误修复而不是显示停止。
就这样吧。以下内容是可重用的,适用于多个上下文,这意味着您可以访问数据库并在客户端中通过两行实际代码获取一些内容。
DataModel(类库项目)
包含 DbContext POCO 等的 EF Code First 项目。
DbContextManagement(类库项目)
DbContextManager.cs
DbContextScope.cs
FacadeBase.cs
ScopedDbContextManager.cs
UnitOfWorkScope .cs
Facade(类库项目)
YourEntityFacade.cs
TestConsole(控制台应用程序) Project)
App.config
Program.cs
因此,用法非常简单,您可以在一个范围内使用多个上下文和外观。使用这种方法,您编写的唯一代码就是自定义查询。不再用存储库引用和创作复制存储库无休止地更新 UnitOfWorks。我认为这很棒,但请注意,这是测试版代码,我确信它在某个地方有一个大洞需要堵塞:)
感谢所有人,特别是拉迪斯拉夫对这个问题以及我提出的许多其他相关问题的耐心和帮助。我希望这段代码引起人们的兴趣。我通过上面的博客联系了作者,但还没有回复,这些天我认为他对 NHibernate 很感兴趣。
理查德
With a very large nod to the author of the original code in the link given above, here is what I ended up with. It passes basic scenarios but I haven't yet tried out deeper navigational and related queries. Even if there is an issue, I reckon it will be bug fix rather than show stop.
Here goes. The following is reusable, works with multiple contexts and means you can go to the database and get something back in 2 lines of actual code in the client.
DataModel (Class Library Project)
Your EF Code First project with DbContext POCOs, etc.
DbContextManagement (Class Library Project)
DbContextManager.cs
DbContextScope.cs
FacadeBase.cs
ScopedDbContextManager.cs
UnitOfWorkScope.cs
Facade (Class Library Project)
YourEntityFacade.cs
TestConsole (Console Application Project)
App.config
Program.cs
So, usage is very simple and you can work with multiple contexts and facades within a scope. With this approach, the only code you are writing is custom queries. No more endless updating UnitOfWorks with repository references and authoring copy-cat repositories. I think it's great but be aware this is beta code and I'm sure it has a large hole somewhere that will need plugging :)
Thank you to all and in particular Ladislav for patience and help on this and many other related questions I ask. I hope this code is of interest. I contacted the author at the blog above but no reply yet and these days I think he's into NHibernate.
Richard