How j0rgemiranda/libreria.modelos works
Project type and purpose
• This is a full-stack ASP.NET Core solution named “Libreria” for managing a library’s data (autores, libros, editoriales, paises).
• It consists of:
• A class-library (Libreria.Modelos) containing domain POCOs.
• A RESTful Web API (Libreria.API) exposing CRUD endpoints.
• An MVC Web App (Libreria.MVC) providing an HTML UI.
• A small console API consumer (Librerria.API.Consumer) for direct API calls.
• A test project (Libreria.Test) for automated tests.
File structure
• Top-level solution (.sln) references four main projects.
• “Libreria.Modelos”: domain entities (Autor, Libro, Editorial, Pais).
• “Libreria.API”:
• Controllers folder (AutoresController, LibrosController, etc.).
• Data folder (AppDbContext + EF Core migrations).
• appsettings.json, launchSettings, HTTP-client script.
• “Libreria.MVC”:
• Controllers and Views organized by entity.
• wwwroot for static assets (Bootstrap, jQuery).
• Shared layouts, view imports.
• “Librerria.API.Consumer”: simple CRUD console app.
• “Libreria.Test”: test harness.
README
• README only names “Libreria.Modelos”. No extra architectural guidance.