Excellent effort for new cummers, Especially those who want to learn clean architecture. Can we include DTOs? We usually include connection strings in our appsettings.jons file and during the video training you mentioned that you'd explain it but not explained. If possible, please add a block diagram and flow chart to explain the concept. I feel complexity when you are using and injecting classes. If you can include some tips. Thanks for your efforts.
Thanks so much for this video... Expecting more of it. I notice tou didn't use the service folder to abstract the business logic, is it not a good practice
Can we acheive the same result with only using Repostory Pattern? then why we need to use Mediatr + CQRS Pattern? and advantage of these pattern? and also please explain use case when to use Mediatr + CQRS Pattern
Hey brother @WebGentle, Thank you so much for putting such brilliant video, very easy to understand. Just one question, don't you think clean architecture is just adding extra complexity , we can accomplish same with on service class for any business logic and repository to communicate to db . What extra benefit I get through clean architecture. Please explain and dont mind if my question is stupid.?
You are totally right. Most of the time it is like additional complexity and thats why it is not suitable in all situations. Take it as just another architecture and use only when it is really needed to keep everything separate.
Nitish mentioned this in the first few videos that all the interfaces and models referenced by other layers must go into Core. The Core is also known as your Domain layer -- think of it as a map of your whole application.
![[MV] A leap of faith...ความเชื่อใจครั้งสุดท้าย (From "Petrichor the series")](http://i.ytimg.com/vi/U1piZH2CNXA/mqdefault.jpg)
The best explanation for Clean architecture, love the fact that you did a simple example with it, and detailed. keep up the awesome vids.
Thank you very much!
The best explanation for WebAPI Clean Architecture
Thank you very much for the tutorial. Nice explanation
Quality full content in DotNET World!
Thank you so much Brother!
Thank you
Another great video!!!!!! Thank you!
Great video sir
Excellent effort for new cummers, Especially those who want to learn clean architecture. Can we include DTOs? We usually include connection strings in our appsettings.jons file and during the video training you mentioned that you'd explain it but not explained. If possible, please add a block diagram and flow chart to explain the concept. I feel complexity when you are using and injecting classes. If you can include some tips. Thanks for your efforts.
Good Explanation
Excellent sir
Great content so how can implemented unit and integration Test for Clean Articture
I ve been waiting for this.
Thats great. I am sure you will love this video. And dont forget to share your feedback about this video after watching it.
Nitish
Thanks so much for this video...
Expecting more of it.
I notice tou didn't use the service folder to abstract the business logic, is it not a good practice
Jai hind sir🙏
Aap ka video bahut helpful hota hai sir.
Sir please make a video on implementing search and pagination feature in .net web api. pls pls thanks in advance. 😀😀
Ab sir app hindhi me video nahi banate hai england chale gaye hai kya sir hindhi me bhi video bana do web api ki
Can we acheive the same result with only using Repostory Pattern?
then why we need to use Mediatr + CQRS Pattern? and advantage of these pattern?
and also please explain use case when to use Mediatr + CQRS Pattern
thankyou sir🎉
Thank you
Hey brother @WebGentle, Thank you so much for putting such brilliant video, very easy to understand. Just one question, don't you think clean architecture is just adding extra complexity , we can accomplish same with on service class for any business logic and repository to communicate to db . What extra benefit I get through clean architecture. Please explain and dont mind if my question is stupid.?
You are totally right. Most of the time it is like additional complexity and thats why it is not suitable in all situations.
Take it as just another architecture and use only when it is really needed to keep everything separate.
You have created IRepository in core layer where some places people create it in Application layer. So which one is correct way..
Repository is a domain so it should be under core
I build it with no problem and when I do post request to addemployee I get 404 Error: Not found
By the way I solve it by adding in the Program.cs `app.MapControllers();`
Why we added interface in core library... can't we add in infrastructure library Directly...can you please explain... thnks in advance ❤
Nitish mentioned this in the first few videos that all the interfaces and models referenced by other layers must go into Core. The Core is also known as your Domain layer -- think of it as a map of your whole application.
Sir please also make a version of webapp ie along with view.
Sure. Lets first learn some advanced concepts about organization level projects then will impleent them in web app too.
First like and comment ❤
Thankyou Mr Deepanshu 🙏
Please make .net core web api + angular course
Hello Mr Qureshi, here is the complete angular course th-cam.com/video/VC_v8QmhyfA/w-d-xo.html
First comment
Thanks 🙏