Entity Framework

 Entity Framework's performance is enhanced by following these steps: Choose the right collection for data manipulation. Do not put all DB objects into one entity model. When the entity is no longer required, its tracking should be disabled and altered. Use pre-generating Views to reduce response time for the first request. Don't fetch all fields unless needed. Whenever possible, avoid using Views and Contains. Bind data to a grid or paging only by retrieving the number of records needed. Optimize and debug LINQ queries. Whenever possible, use compiled queries.

  DbContext is referred to as a class in the Entity Framework API that helps create a communication between the database and the domain/entity class. In simple terms, it is a class mainly used for communicating with the database. DbSet is also referred to as a class that helps represent an entity set for different operations, such as creating, updating, reading, and deleting. The context class in DbContext must include the DbSet type properties for all such entities that help join database tables and views.

  Entity Framework is injection safe since it always generates parameterized SQL commands which help to protect our database against SQL Injection. A SQL injection attack can be made in Entity SQL syntax by providing some malicious inputs that are used in a query and in parameter names. To avoid this one, you should never combine user inputs with Entity SQL command text.

 Ans. A SQL injection attack is an attack mechanism used by hackers to steal sensitive information from the database of an organization. It is the application layer (means front-end) attack which takes benefit of inappropriate coding of our applications that allows a hacker to insert SQL commands into your code that is using SQL statement. SQL Injection arises since the fields available for user input allow SQL statements to pass through and query the database directly. SQL Injection issue is a common issue with an ADO.NET Data Services query.

There are two types of persistence scenarios in the entity framework: 1. Connected Scenarios In this scenario, the same context class is used to retrieve and save entities. It keeps track of all databases during the whole lifecycle. It is useful for the databases for the same network. 2. Disconnected Scenarios In this scenario, a different context is used to retrieve and save data. One instance of context class is used to retrieve the data, and another is used to save the data.

 There are two types of entities in an entity framework: 1. POCO Entities (Plain Old CLR Objects) It is an entity class that does not depend on any framework-specific base class. It is the normal .NET CLR class that's why it is named "Plain Old CLR Objects". It supports many operations like update, create, and delete that are generated by the entity data model. 2. Dynamic Proxy Entities (POCO Proxy) Dynamic proxy entities are runtime classes and wrap up the POCO entity. These entities are lazy loading classes. It is only supported by EF 6; EF Core 2.0 does not support it yet.

  Entity framework is an Object Relational Mapping (ORM) framework that offers an automated mechanism to developers for storing and accessing the data in the database. Its purpose is to abstract the ties to a relational database, in such a way that the developer can relate to the database entity as to a set of objects and then to classes in addition to their properties. Entity Framework Development Approaches: There are mainly three approaches to create entity frameworks: 1. Code First Approach 2. Model First Approach 3. Database First Approach The Entity Data Model: The entity data model (EDM) is made up of three parts: Conceptual Model: The conceptual model represents the model classes (also known as entities) and their relationships. This will be independent of the database table's architecture. It describes your business objects and their relationships in XML files. Mapping Model: A mapping model specifies how the conceptual model is translated into a storage model. The Mappi...