We did this because we will be converting this class into a database table and the column EmployeeId will serve as our primary key with the auto-incremented identity.
Additionally, we have decorated the EmployeeId property with Key and DatabaseGenerated attributes. The code above defines the class Employee with some properties. Let’s add a new class Employee.cs inside: We will start by creating a folder Models within the root of the application. Generating the Database from Code Using Migrationsįirst, let’s define the model.
Once we have set up the project, the next step is to set up the EF Core.įollowing are the steps for configuring the EF Core: NET Core with SignalR and Angular – Real-Time Charts ASP.NET Core Web API with EF Core DB-First Approach.So we should make changes to the code only. The important thing to note is that the manual changes that we make to the database could be lost during migration. We can just make the changes in our code and then sync everything easily with the database. We don’t have to worry about creating and updating the database. This approach is helpful in situations where we are starting with the development of a new project and we don’t have a clear picture of how our database should look like yet. In the EF Core Code-First approach, we have full control over the code and the database is just a store without any logic. This is the opposite of the Database-First approach where we design our database first and then create the classes which match our database design. Later, we’ll create the database from our code by using migrations. While working with the EF Core Code-First approach, we create the classes for our domain entities first.
0 kommentar(er)
