Three Types of Entity Framework?

Pages 157 to 161 of "ASP.NET Core 2 and Angular 5" by Valerio De Sanctis have a pretty good breakdown. Model-First is the old way of doing things with an .edmx. EDMX stands for Entity Designer Model XML visual interface and the book also name drops XML-based DataSet Schema and gives the acronym XSD though I suspect that is yet another typo in the book and that XDS is meant. I guess the XDS files are the XML mapping files the .edmx makes as you model stuff with it. In the Database-First approach we build a database and then let everything else autogenerate reactionarily off of that including, to my surprise, an .edmx by way of what the book suggests is the Entity Framework Designer tool. In the Code-First approach apparently there is an attribute-based way to override default mappings at your classes which autogenerate everything else to specify differentiations at the database such as a different name for a column I suppose. Since version 4.3 of Entity Framework there has been migration support to account for the data loss that might come with dropping and recreating a database in the Code-First approach and the book warns of a terrible learning curve which seem consistent with what I have experienced myself.