Видео

Excellent video!! I would like see more but now about DDD from scratch upto the point too.

Let me put my perspective into context. I've been a software developer since before DOS 1.0 and now use MS tools and technologies exclusively. It was very disappointing when MS made the choice, for the most part, to stop providing written documentation and examples on thier tools and technologies. The results was an explosion of 3rd parties trying to fill the gap. Many of which were only interested in putting up a blog or website to make a name for themselves or generate revenue from ad impressions. These had little if any useful information in them and if they did it was often so brief as to be useless, inaccurate or out dated. To some degree the same can be said about RUclips videos. But generally speaking, its not nearly as bad since the motivation for selling ad impressions has been taken off the table. That means, if the RUclips author can't deliver a better experience, one that has real world value, there won't be a lot bell ringing. I can count on two hands the number video channles I'm still subscribed to after 20 years. But, after watching two if your videos, I rang that bell because it was clear you were here to do what you claimed and you were doing it well. Nice job and I look forward to more, may even leave a suggestion on some topics at some point in the future.

Thank you!!!

How would you deal with concurrency in something like this? For example, what if there were multiple users on the edit customer page updating the same record.

Found this quite helpful as a beginner, thanks for the video!

Enlightening lecture

can you make the video of blazor server UI implementing this?

Thanks you so much ❣️

Thank you. It was more comprehensible more then Turkish channels.

well presented

bbb

please share Dto page and Service Page Code

Hello; I thank you for this good series of tutorials.❤ But I think sharing the videos of this tutorial series faster can help your audience a lot.

it should be domain aka Entities <= Application aka Use cases <= Presentation aka API <= Infrastructure I don't know why you implement Infrastructure by using Application layer

Thanks for explaining, but if we have tons of Repositories? do we have to register them all in Program.cs by this the lines of code in Program.cs will increase so much which is bad in terms of scalability

Thank You very much.

Thank you for this great tutorial.

can you explain 2:58? I've got a red line under "DbContext" and cannot go to its definition

Please bring back this series, i need it !

how to bring in their dependencies as you said

24:30 that exact time brought up a window and i feel i lost a very important info on how to bring up that window and do as you did

Maybe you forget to instruct to add some code in program.cs in API such as: builder.Services.AddScoped<IMovieService, MovieService>(); builder.Services.AddScoped<IMovieRepository,MovieRepository>(); When I add that, Visual Studio suggest me to add project reference from WebAPI project to Infastructure Project. It may break the concept clean. How to avoid to do that?

Cool video. Do more for .NET 9

Cool video. Do more for .NET 9

beautiful class

tks man

there is no explanation in the video where you register the two dependencies needed for the repository pattern, to be added to the builder, but!, if you pause the video in [27:33] you can see it the 2 dependencies added to the builder.

Thanks for the video. Nice one.

Application layer is using infrastructure right. Then application should be dependent on infra, not vice versa. Please elaborate

Clean presentation for clean architecture...☕☕☕

I can't believe these terrible patterns seem to be standard practice now. This is a sure way to make projects vastly over complicated and unnecessarily complex.

this is not very beginner friendly though, you skip quite some important information (you type something, but you don't explain why you wrote it, why not a different way, or what it does). Also the database part, i would actually use a real database, so it is more aligned with real world usage

Thank you very much, you explained very well. But next time please do not add the background music, or you can use as in lower volume.

Hi Simuzeche. Thank you for the "Secure Your .NET 8 Web API with JWT Bearer Authentication (Step-by-Step)" video. In this video, you mentioned that you have a separate video that shows how to implement a "Refresh Token". But, I cannot find it. Can you send the link to the 2nd video ? Any idea when you'll have the "How to Refresh Token in .NET 8 Web API" ? I've been waiting a while on this one. Will you be putting that video out under RUclips ?

I had a blast

Thank you so much, this article is very useful for me.

This was one of the best tutorial videos for introducing web api development for .NET I have have ever watched in my 6 years of software engineering

thank you very much for your "Clean explanation" of Clean Architecture concept.

your series are about to come in hand for our upcoming project, keep making more of these 🙏🏾🙏🏾

Perfect teaching!

Although using ServiceLifetime.Transient is valid, it’s generally recommended to use ServiceLifetime.Scoped for DbContext to ensure one instance per request. Using transient lifetime for DbContext can lead to multiple instances per request, which might not be efficient.

The intro has been on-point!! Covering the overview. I have been a developer for a while but need to really get everything right this time. I'm not sure if your goal for this tutorial series is to build an industry standards production level web API but would be following it till the end hoping it includes everything from authorization, authentication, oauth/oauth2 tokens, building robust and non blocking APIs with best practices, some sort of queuing for requests, security best practicies, creating and passing DTOs, seperating the service layer and business logics, implementing the data model layer, some sort of caching for performance, ORMs to handle database requests, filtering, minimizing database requests, repsonse handling etc etc Also, one challenge I faced was not able to understand how the requests were going through the IIS in a microservices architecture and also when requests coming in from outside client. I have high hopes from this!! Tired of searching the internet for one coherent and comprehensive series to make me a reliable and competent .Net developer. Please help to this cry! Incase you can point me to the right resources I would appreciate or even better if you have the bandwidth to assign tasks that I can complete in sequences. NOT LOOKING FOR A ROAD MAP.!! Thanks and super like for you, Already liked shared and subscribed!!!

factastic please make a more videos on clear artitecture and thats type of things

in design picture, there is no reference from WebApi to Infrastructure, but in code why there is a depedency reference from WebApi to Infrastructure

Very helpful. Excellent! Thank you.

Finally a clear explanation of clean architecture. Thanks ! When we set the dependency injection in the api layer we must reference the movierepository in the infra. I thought we only communicate with application layer from api. please explain

I Think Migration should be in Infrastructure

Thanks for the detailed and clean explanation. Please continue your good work

This is awesome , thank you so much