Register now or log in to join your professional community.
Entity Framework with linq methods makes easier and simple
Thanks to all for given answer
First of all, Entity Framework relies on ADO.NET for data operations.
Best practices recommend n-tier application architecture. That means you need to "usually" create three sets of classes, that is; data model, business logic, and presentation / view. Entity Framework would automatically create the "data model" classes for you, then it provides you with tons of ADO.NET-based methods to handle your database through these classes.
Entity Framework, however, has some drawbacks in quality and limited capabilities, which puts you in front of some choices:
- You may search for suitable NuGet add-ins to resolve your issues.
- You may improve and extend its features.
- You can still use ADO.NET directly to bypass the issue. (I don't prefer it)
Therefore, whether you decided to use Entity Framework to create your data model, or you chose to create it your self, ADO.NET is part of the game after all.
Finally, it is recommended for fresh developers to rely on Entity Framework, because it would keep your code well organized, maintain several quality aspects, and saves you a lot of coding time. Later, as you get more experience with different problems and scenarios, you can choose your own path.
You can use some Micro ORM like Dapper or Insight Database, these two are simple, good and fast, since Entity Framework is heavy and takes more memory. If data grows it slow down the app.
Entity Frame work is better option
the business is what determines what you need to work with but if we go to the performance the entity framework performance is better than the ado.net
and you can use ado.net query through Entity FrameWork
Do you need help in adding the right keywords to your CV? Let our CV writing experts help you.
