If we need to access a database from our application we need a persistence framework. With the persistence framework we will be able to load our objects from database or save them to database.
We can write the persistence framework by ourselves using plain ADO.NET classes’ like-
Or we can also use an existing persistence framework.
Writing a persistence framework from scratch is very costly. We have to
- Write a lot of Stored Procedures
- Read the data using ADO.NET objects
- Manually Mapping database tables and records to the domain objects of our application
That’s why we can use Entity Framework.
Entity Framework is a persistence framework that frees us from all above dirty works. If we use Entity Framework then we no longer have to
- Write Store Procedures (in most cases)
- Manage Database Connections
- Manually Mapping database objects and records to domain models of our application
Entity Framework takes care of all of these for us.
So in shortly we can say-
Entity Framework (EF) is an object-relational mapper that enables .NET developers to work with relational data using domain-specific objects. It eliminates the need for most of the data-access code that developers usually need to write.
CSM, CSPO, CSD, CSP-SM, CSP-PO (ScrumAlliance.org)
Certification Profile Link-
Currently working as Lead Team (Application Architecture) at Raven Systems Ltd. Passion for software development especially agile practices such as TDD with in depth knowledge of Object Oriented Programming, SOLID Principles, Gang of Four Design Patterns, Some Enterprise Application Architectural Patterns. Over 8 years of software development experience ASP.NET. Has the ability to understand and transform complex business requirements into software ensuring applications are delivered on time. Also experience in non Microsoft .NET technologies such as Dapper.Net, Git, Structure Map & Angular, Bootstrap, HTML-5, CSS-3 etc.