有关使用实体框架分支/合并项目的任何担忧
我即将分支一个使用 EF 的项目。我知道主干会有一点变化，分支也会有很多变化。我需要不时地将更改从主干合并到分支中。
我不关心使用 EF 对象（Linq to Entities）的直接 C# 代码，我关心实体模型本身？
I'm about to branch a project that uses EF. I know that there will be a modicum of changes in the trunk, as well as many changes in the branch. I will need to merge in changes from the trunk into the branch from time to time.
I'm not concerned about the straight up C# code that usese EF objects (Linq to Entities) I'm concerned about the entity model itself?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
EF 实体模型的分支/合并/并发开发故事是一个众所周知的痛点。我认为在自动合并失败的情况下，您只需要手动合并差异。或者，您可以使用 EF 4 中添加的仅代码方法，完全忘记实体模型。
如果您还没有查看过此相关问题，您可能想查看一下：
Entity Framework Merge Nightmare
The branching / merging / and concurrent development story for EF entity models is a known sore spot. I think you are just going to have to manually merge the differences in the cases when automerge fails. Alternatively, you could go with the code only approach added in EF 4 and forget about entity models altogether.
You may want to check out this related question if you haven't already:
Entity Framework Merge Nightmare