MVC

I think the differences are:

Code first

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.

Database first

Very popular if you have DB designed by DBAs, developed separately or if you have existing DB.
You will let EF create entities for you and after modification of mapping you will generate POCO entities.
If you want additional features in POCO entities you must either T4 modify template or use partial classes.
Manual changes to the database are possible because the database defines your domain model. You can always update model from database (this feature works quite good).
I often use this together VS Database projects (only Premium and Ultimate version).

More details follow http://roland.kierkels.net/c-asp-net/ef-model-vs-database-vs-code-first-approach/

2 Replies

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

Manas Mohapatra10y ago
Choose between DB first and Code first is based on scenario. Means if you already entity classes in your project then Code first is suitable, in other way if you already have database then DB first approach is suitable.

Moreover follow below link:

http://www.entityframeworktutorial.net/choosing-development-approach-with-entity-framework.aspx
Shakti Singh Dulawat10y ago
I think the differences are:

Code first
- 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.
Database first
- Very popular if you have DB designed by DBAs, developed separately or if you have existing DB.
- You will let EF create entities for you and after modification of mapping you will generate POCO entities.
- If you want additional features in POCO entities you must either T4 modify template or use partial classes.
- Manual changes to the database are possible because the database defines your domain model. You can always update model from database (this feature works quite good).
- I often use this together VS Database projects (only Premium and Ultimate version).
More details follow http://roland.kierkels.net/c-asp-net/ef-model-vs-database-vs-code-first-approach/