EF 4.1 代码首先使用现有数据库。映射 Fks、表等。需要澄清
我首先学习代码，并且我有一个要与现有数据库一起使用的项目。
我对我想要做什么有点困惑。我将解释：
- 我是否需要为现有数据库中的每个表创建一个实体配置？
- 在每个表的 EntityConfiguration 中，我是否需要创建外键关系？
- 我需要为现有数据库中的每个表执行 ToTable 吗？
- 是否有任何免费工具“codeplex”指向现有数据库会生成此 codeFirst 内容？
我似乎很少有关于“现有数据库的 EF Code First”的博客，但我不确定或不清楚我是否需要创建这个东西，否则我会收到像“MyColumn_MyColum”这样的奇怪错误，基本上就好像 codeFirst 正在尝试构建一样一些FK什么的。
有人可以澄清一下吗？ 多谢。我知道问题很少，但如果你能回答 01 或 2 那就没问题了。
再次感谢
I am learning code first and I have project to be used with an existing database.
I am a bit confused of what I meant to be doing.I will explain:
- Do I need to create an entityconfiguration for each table in my existing database?
- Within this EntityConfiguration for each table do I need to create foreign key relationships?
- Do I need to do a ToTable for each table in my existing database?
- Is there any free tool "codeplex" that pointing to an existing db will generate this codeFirst stuff?
I have seem few blogs about "EF Code first with existing db" but I am not sure or was not clear to me If Need to create this stuff or I will be getting strange errors like "MyColumn_MyColum" basically as if codeFirst is trying to build some FKs or something.
can somebody clarify?
thanks a lot. I know there are few questions but if you can answer 01 or 2 that would be fine.
thanks again
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您希望生成代码，请使用 使用 DbContext API 的数据库优先方法。只需从数据库创建 EDMX 文件，然后让 DbContext Generator 模板为您生成所有实体和上下文。
DbContext Fluent API 主要针对代码优先的开发方法，其中 EF 将根据您提供的代码为您创建数据库。它可以与现有数据库一起使用，但需要 EF 为您提供的更多技能和对映射的理解。
一般来说：
EntityConfiguration命名为 Id 或 EntityNameId 等）。ToTable。EF 使用许多默认约定 驱动名称的定义方式。约定可以被删除。
如果您为每个表定义EntityConfiguration，您将不会做任何错误 - 它至少可以让您了解需要什么，并且您的映射将是明确的/自记录的。
If you want the code to be generated for you use database-first approach with DbContext API. Simply create EDMX file from your database and let DbContext Generator template generate all entities and context for you.
DbContext Fluent API is mainly targeted to the code-first development approach where EF will created database for you from the code you provided. It can be used with existing database but it requires much more skills and understanding of mapping wich EF can provide to you.
Generally:
EntityConfigurationfor each table if you follow some naming conventions (entity name is singular form of table name, all properties have the same name, primary key in table and entity is named as Id or EntityNameId, etc.).ToTableis needed only if your entity does not follow naming convention or if you map some advance inheritance or splitting.EF uses a lot of default conventions which drive how the names should be defined. Conventions can be removed.
You will not do anything wrong if you define
EntityConfigurationfor each table - it will at least allow you learning what is needed and your mapping will be explicit / self documented.