Getting Started with .NET Core Clean Architecture (Udemy.com)

good explanation.

The solution diagram in video 1 illustrates folders (namespaces) that scream "dependency magnets." Instead of having namespaces defined by responsibility, they are defined by file types (e.g., Interfaces, POCOs, etc.). I will keep watching with hope that this is cleaned up. But that slide contradicts what is taught in Robert Martin's book, Clean Architecture. See chapter on "Screaming Architecture."
Update: While this course is a decent introduction to .NET Development, Layered Architecture, MVC, "Coding to an Interface", and Dependency Injection; it's still not really a lesson on Clean Architecture. (I've bumped this up from one to two stars.)

NO

Good introduction, simple, but IoC layer has to be better explained for beginners, Isn't inside .Core?

Many thanks for your course, Mr. Manish. This course is a big help for me to coding more clean and well organized.

This is not what i expected from the title

Nice course about implement clean architecture and more

I just started so i don't know if it is a good match.

1. Wasted time on GitHub - not signed up for that
2. Wasted time again on Identity
3. Wasted time over and over on build and update code
4. Wasted time on insert data, it could just be edit the table and insert the data - keep in mind we are interested on clean architecture not managing the course.
5. What is cover in 4 to 5 hours can be cover in 90 minute and 1/3rd of the lecture.
6. It was not worth it, because what was present can be found in you-tube even more clear instructions. I think course was created in rush and stressed to make it bigger. More importantly the course is not production ready and quality code.

Helped me a lot as I am a beginner...

This must be one of the worst courses I ever subscribed to. The author gives you the impression that the whole project wasn't planed and he explains what he's doing to as if he's trying to explain it himself while he's reading somebody else's code. It is very easy to get lost in the overwhelming details that he's provides you with. The author filed to stick with the flowchart he drew at the beginning of the course, and he provides almost no theoretical explanations about the adopted architecture. Writing a code that nobody understands its flow except you is not a clean architecture. Not recommended.

I think it can be improved with a better explanation of the patterns, with diagrams maybe. Yet, it was a good course... Thanks a lot!"