Last post Jul 17, 2018 09:07 PM by DA924
Jul 17, 2018 07:01 PM|mazhar khan india|LINK
Jul 17, 2018 07:16 PM|Mikesdotnetting|LINK
Your requirements are irrelevant to your decision. You would use Database First if you are working with an existing database. If you don't have a database, you should use code first to generate the database and then use migrations to keep your database schema
in sync with your model. You can also use code first with an existing database, which is also recommended above database first. The Database First approach has been dropped entirely in ASP.NET Core.
Jul 17, 2018 07:32 PM|mazhar khan india|LINK
Jul 17, 2018 08:13 PM|Mikesdotnetting|LINK
If you prefer to work with data as objects, use EF. If you are happy with DataReaders and DataTables, use ADO.NET.
Jul 17, 2018 09:07 PM|DA924|LINK
mazhar khan india
I am using visual studio 2013 and I tried some example using database first. Shall I have to go with database first using entity framework, one more doubt database first using entity frame or ado.net which one is good..
If you going to go what ADO.NET, then go with SQL Command Objects, parametrized inline T-SQL, parametrized stored procedures, a datareader a custom type like a DTO or DTO(s) is a collection for CRUD operations with the database.
You know that's what an ORM like EF is really doing is the above under the hood.
Myself, I have never had a problem with database first. I have seen a whole lot of people have problems with code first, becuase they don't have a good grasp on object oriented programming, and they don't database administration 101, just out there winging