programming in Model first approach

Rahul Pal

11y980.NET

I am a new to MVC an I am practising a from the basics. I have found some sample from web using codefirst approach or database first approach but. "REGISTRATION PAGE AND LOGIN FORM USING MODEL FIRST ", i am not able to do. So i need some help. please help.

Also would like to more about the advantages and disadvantages of this approach with respect to other approach

3 Replies

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

Priyaranjan K S11y ago
Rahul,

In Model first we design the DB model and then generate a database and classes based on the model.

You can also check out this step by step demo :

http://www.c-sharpcorner.com/UploadFile/abhikumarvatsa/model-first-approach-in-entity-framework/

http://www.youtube.com/watch?v=UNt3uWqMdMU

http://www.youtube.com/watch?v=BOrLrvEtAfw

Thanks,
Priyan

If you found this useful Please Accept this as Answer.
Rahul Pal11y ago
@Priyan : Thanks for your quick reply. Its really good to know these stuffs. But My real question was related to model first. Hope if u can throw some light on it also. some code is very much for me. Thanks again
Priyaranjan K S11y ago
Hi Rahul,

The fundamental difference is in Code First you design the DB in your code . This gives you full control over the code and design . In DB first approach you already have a DB designed to you by the designers. Now you have to develop you code based on that design .
Detailed Difference :
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).
Why developers prefer code first : http://www.itworld.com/article/2700195/development/3-reasons-to-use-code-first-design-with-entity-framework.html

You can refer these links to get you started :
Code First
http://www.codeproject.com/Articles/826571/Code-First-Approach-with-ASP-NET-MVC-Framework
http://www.c-sharpcorner.com/UploadFile/abhikumarvatsa/code-first-approach-in-entity-framework/

Data Base First 3 Part Series :
http://www.c-sharpcorner.com/UploadFile/4b0136/database-first-approach-in-mvc-5-working-with-database/

Thanks,
Priyan

If you found this useful Please Accept this as Answer .