Go to books ↓
ASP.NET Core and Entity Framework Core are getting more and more attractive nowadays and this post will show you how to get the most of them in order to get started with building scalable and robust APIs.
While EF Core attempts to keep the paradigms and much of the syntax of earlier versions of Entity Framework, EF Core is a new set of APIs—a completely new code base written from scratch. Therefore, it’s important not to presume that everything will behave exactly as it did in the past. The change tracker is a critical case in point.
The reverse engineering of your database takes the form of scaffolding a context class and all the entity (or POCO classes) classes. Scaffolding just means code generation. It will generate the class files for you in the project.
All ASP.NET Core Identity needs is the required database tables to support its huge set of features. And believe me, you won’t have any performance penalties for using a simple DbContext accessing a few tables in the database. On the other hand, you will be able to use out of the box a set of membership features (proven security algorithms, token based authentication, external logins, Two-Factor authentication and much more..) that you would spend months to implement on your own.