How to structure a clean architecture Asp.Net Core app

What goes where? That's the question I get a lot when it comes to structuring a #DotNet application according to the clean architecture principles. Further, "clean architecture" has become a buzzword that everybody is using, but few really understand the concept behind it. In this video we start from the basic principles of clean architecture and then we structure a new #AspNetCore app according to these principles. On this journey we also compare a lot what is different in this clean architecture approach compared to the standard n-layer / n-tier approach. #softwarearchitecture Join this channel to get access to perks: If you want to support this channel, here's a link to my GitHub Sponsors profile: https://github.com/sponsors/danpdc Mentioned videos: How to structure a layered Asp.Net Core app? https://www.seevid.ir/fa/w/S86Y0sxXhDE Repository pattern with Asp.Net Core API: https://www.seevid.ir/fa/w/QU2QzPDh3-I Chapters 1. Intro https://www.seevid.ir/fa/w/ZXGiactmoj0 2. Clean architecture principles: https://www.seevid.ir/fa/w/ZXGiactmoj0 3. Different approaches to clean architecture: https://www.seevid.ir/fa/w/ZXGiactmoj0 4. Modeling the domain (core) layer: https://www.seevid.ir/fa/w/ZXGiactmoj0 5. Modeling the use cases (application) layer: https://www.seevid.ir/fa/w/ZXGiactmoj0 6. Where we put services and where do we put repositories? https://www.seevid.ir/fa/w/ZXGiactmoj0 7. Modeling the infrastructure layer: https://www.seevid.ir/fa/w/ZXGiactmoj0 8. Modeling the presentation layer (API): https://www.seevid.ir/fa/w/ZXGiactmoj0 9. Understanding your project dependency graph: https://www.seevid.ir/fa/w/ZXGiactmoj0