Fun Project #6: ASP.NET Core CRUD Web API with Repository Pattern, SQLite, UnitOfWork & Swagger For APIDocs

Had some fun on this one. My motivation was to spend some time digging deeper into how C# & ASP.NET thinks about every line of code you write.

Examples:

1. Automapper is widely used to map Entities to Requests or Responses, but when you create mappings, how does it know where to look to find your mapping profiles?

In ASP.NET Core, AutoMapper typically gets configured during application startup, and it automatically scans the assembly for mapping profiles. When AutoMapper is initialized, it scans for any classes derived from Profile and adds them to the configuration.

2. Many ASP.NET devs separate their projects into class and service libraries, but is this always a must? Do you break anything if you don't do it like that? What are the pitfalls of having all your logic in a single project?
3. How about the .NET workflow itself? Why will you leverage on the dotnet CLI instead of building your project in Visual Studio?

In your career as a software engineer, at some point, you will come across challenges that require you to go beyond syntax, and deeper into bare-metal, and my fun projects are ways I take time to go into the underlinings of every tool I use.

Hope you like this one 😊

GitHub - ekowamoonu/formula_one_api: ASP.NET Core Web API CRUD, Repository Pattern, SQLite & Automapper

ASP.NET Core Web API CRUD, Repository Pattern, SQLite & Automapper - ekowamoonu/formula_one_api

GitHubekowamoonu