Regarding EF code first, db first and model first

Code First: In the Code First approach, you avoid working with visual model designer (EDMX) completely. You write your POCO classes first and then create database from these POCO classes.

Developers who follow the path of Domain-Driven Design (DDD) principles, prefer to begin by coding their domain classes first and then generating the database required to persist their data.

Very popular because hardcore programmers don't like any kind of designers and defining mapping in EDMX xml is too complex.
Full control over the code (no autogenerated code which is hard to modify).
General expectation is that you do not bother with DB. DB is just a storage with no logic. EF will handle creation and you don't want to know how it do the job.
Manual changes to database will be most probably lost because your code defines the database.

Model First: In the Model First approach, you create Entities, relationships, and inheritance hierarchies directly on the design surface of EDMX and then generates

IMHO popular if you are designer fan (= you don't like writing code or SQL).
You will "draw" your model and let workflow to generate your database script and T4 template to generate yout POCO entities. You will lose part of control on both your entities and database but for small easy projects you will be very productive.
If you want additional features in POCO entities you must either T4 modify template or use partial classes.
Manual changes to database will be most probably lost because your model defines the database. This works better if you have Database generation power pack installed. It will allow you updating database schema (instead of recreating) or updating database projects in VS.

If its useful, mark it as "Accepted Answer"

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

11y ago
it would be much better if you provide link for code first and model first approach because i never use EF. so i need to know this from basic to advance level. so give articles link for code first and model first for beginner like me who never use EF in any project. thanks
0
Tom Mohan11y ago
Code First: In the Code First approach, you avoid working with visual model designer (EDMX) completely. You write your POCO classes first and then create database from these POCO classes.

Developers who follow the path of Domain-Driven Design (DDD) principles, prefer to begin by coding their domain classes first and then generating the database required to persist their data.
- Very popular because hardcore programmers don't like any kind of designers and defining mapping in EDMX xml is too complex.
- Full control over the code (no autogenerated code which is hard to modify).
- General expectation is that you do not bother with DB. DB is just a storage with no logic. EF will handle creation and you don't want to know how it do the job.
- Manual changes to database will be most probably lost because your code defines the database.
Model First: In the Model First approach, you create Entities, relationships, and inheritance hierarchies directly on the design surface of EDMX and then generates
- IMHO popular if you are designer fan (= you don't like writing code or SQL).
- You will "draw" your model and let workflow to generate your database script and T4 template to generate yout POCO entities. You will lose part of control on both your entities and database but for small easy projects you will be very productive.
- If you want additional features in POCO entities you must either T4 modify template or use partial classes.
- Manual changes to database will be most probably lost because your model defines the database. This works better if you have Database generation power pack installed. It will allow you updating database schema (instead of recreating) or updating database projects in VS.
If its useful, mark it as "Accepted Answer"
0