Register now or log in to join your professional community.
I prefer database first.
1. Because its easy to create tables and relationships.
2. You don't need to write extra code.
3. Easy to update.
Actually, I would prefer the database first approach because :
1. It's simple to create the data model.
2. You don't have to write the table relations your code.
3. It's easier to update the database tables and the data model.
4. Fits for the huge data.
practically, for legacy reason, database-first is the way to go. The database exists, a database admin took care of it. But for MS unknown reasons, code-first is generally better, in the future, because you can just copy and paste scripts that will rebuild from scratch the database. You can mix both, this is what I do. The idea of database as core is fading. Code will be the new core.
Definately Database first.Because it's easy to define relations like reference keys, primary key, etcetera. Create your database structure and the visual studio will automatically generate the classes from it in entity framework. And after that, its easy to retrieve, put, update, delete DB data using it
I will Choose Data First Approach.
Because its reduces Line of code.
Its easy to create tables and relationships.
I prefer Code First apprach ,
it's make me can use identity authrization and membership.
more easy to update tables ,
and can build the database with table and data if i want to do on application start.
it's perfect.
