多么成熟& felxible 是实体框架的代码优先库吗？
我正准备使用 Scott Gu 引入的 EF 代码优先方法进行一个小型、简短的架构峰值 此处 和 此处。在此之前，我想知道这是否值得。目前，我有一个使用 EF POCO Generation 模板的项目，我想研究一下为域模型切换到更纯粹的 POCO 策略可以获得的优势。特别是，这些是我感兴趣的事情：
- 使用集合修复方法自动生成部分类，并能够专注于基本的域对象代码，而不必担心关联持久性。
避免每次我想向模型添加工件时都必须转换模板。
仍然能够对表持久化策略进行一些控制（ComplextTypes 的位置、每个类型一个表与每个层次结构一个表等）。这些并不像其他两个问题那么重要。
我能找到的最新版本是 2010 年夏季发布的 CTP4。这是最新版本吗？
选择这种方法、使用这个特定的库有什么缺点？您能否建议我应该在峰值中调查的任何其他问题？
I'm getting ready to do a small, brief architecture spike using the EF code-first approach, introduced by Scott Gu here and here. Before I do, I'd like to know whether it will be worth it. Currently I have a project that uses the EF POCO Generation template, and I'd like to investigate the advantages I can get out of switching to a more pure POCO strategy for the domain model. Particularly, these are the things I'm interested in:
Avoiding automatically-generated partial classes with collection fixup methods, and being able to concentrate on essential domain object code without worrying about association persistence.
Avoiding having to transform templates every time I want to add an artifact to the model.
Still being able to have some control over the strategy of table persistence (locations of ComplextTypes, table-per-type versus table-per-hierarchy, etc). These aren't as important as the other 2 concerns.
The most recent version I could find of this was the CTP4, released summer 2010. Is this the most current version?
What are the cons of choosing this approach, using this particular library? Can you recommend any other concerns I should investigate in the spike?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
浏览 这些教程并查看此博客了解一些其他信息像继承这样的主题 - 它将为您提供 CTP5 中 Code First 的很好的概述，它应该接近最终版本，如所述 此处：
我认为当前版本已经满足了您提到的所有三点。
Go through these tutorials and check this blog about some additional topics like inheritance - it will give you pretty good overview of Code First in CTP5 which should be close to final version as stated here:
I think all three points you mentioned are satisfied by current version.