This was super useful. I followed along step-by-step, and I appreciate how you explain things, and even do them "incomplete", like showing how something won't compile because we didn't configure something correctly. That teaching approach really helped me understand without going too fast or getting ahead of the concept at hand.
I really like the covered points for this video, specifically the Authentication-Authorization concerns, for this purpose I bought the course directly, thanks.
Good video. And a good trick to engage us to buy the Udemy course, but actually I did buy it and from my perspective, the course is TOTALLY RECOMMENDED. It goes deeper into Clean Architecture patterns and explains the concepts very well. I hope more content related here and in Udemy. Congrats!
thanks for the feedback, Im glad you liked it :) Im currently fishing up a MS SQL course (but in Polish), but after that I do have a plenty of content to record in English as well, both youtube and udemy courses (such as :entity framework, ASP.NET MVC, Azure services, etc.)
Just started watching this video, I'm going to try to follow thru video, but then afterwards, modify for a ATS system and then much later attach to VMS system. Thanks.
The example you give 9:51 show GET request with a request body. A request body with GET doesn't often work since some libraries don't expect a body with GET.
true, it depends on the library, but it's not explicitly prohibited by the HTTP standard. It's a rare case to use such HTTP request, but since GET URLs have a maximum length limit, which varies across different browsers and servers. Including large amounts of data in the URL query string can exceed this limit, leading to truncation or errors (consider a grid/table that takes multiple parameters for filtering, sorting, pagination- all of those params combined might be simply too big for the query params) In that case you might want to either you GET with a request body, or fetch the data with a POST request - which also feels odd ;p
stuff like mapping, handling the requests, or even command validation belongs to the application layer, you can have a look at the final project Repo: github.com/jakubkozera/Restaurants or follow along rest of the course on udemy
Full course:
fullstackdeveloper.tech/c/web-api-ca
My complete Azure DevOps course:
fullstackdeveloper.tech/c/complete-azure-devops
This was super useful. I followed along step-by-step, and I appreciate how you explain things, and even do them "incomplete", like showing how something won't compile because we didn't configure something correctly. That teaching approach really helped me understand without going too fast or getting ahead of the concept at hand.
Thanks for the feedback
Im glad you liked it
This is a great course and things are working as I am doing it. Normally, courses are not practical but this one seems to promising. Great work!!!
Im glad you like it
I really like the covered points for this video, specifically the Authentication-Authorization concerns, for this purpose I bought the course directly, thanks.
Thanks, glad you liked it
Enjoy the rest of the course
Good video. And a good trick to engage us to buy the Udemy course, but actually I did buy it and from my perspective, the course is TOTALLY RECOMMENDED. It goes deeper into Clean Architecture patterns and explains the concepts very well. I hope more content related here and in Udemy. Congrats!
thanks for the feedback, Im glad you liked it :)
Im currently fishing up a MS SQL course (but in Polish), but after that I do have a plenty of content to record in English as well, both youtube and udemy courses (such as :entity framework, ASP.NET MVC, Azure services, etc.)
@@AzureFullstackDev I would love to see a topic on extending a rest API with clean architecture to support multi tenants.
Just started watching this video, I'm going to try to follow thru video, but then afterwards, modify for a ATS system and then much later attach to VMS system. Thanks.
The example you give 9:51 show GET request with a request body. A request body with GET doesn't often work since some libraries don't expect a body with GET.
Also, I have seen that some firewalls block the request body for GET operations. The POST is for sending body data.
true, it depends on the library, but it's not explicitly prohibited by the HTTP standard. It's a rare case to use such HTTP request, but since GET URLs have a maximum length limit, which varies across different browsers and servers. Including large amounts of data in the URL query string can exceed this limit, leading to truncation or errors (consider a grid/table that takes multiple parameters for filtering, sorting, pagination- all of those params combined might be simply too big for the query params) In that case you might want to either you GET with a request body, or fetch the data with a POST request - which also feels odd ;p
Hi, In the Full Course, when using Identity, Do you make use of JWT during API Auth?
Hi,
Thanks for this course.
Any new Microservices Webapi course something like any clone with entity framework are aligned up ?
1:05:30 you can kill me but i still dont know difference between in IActionResult and ActionResult
Why do you not create a new class for Contact? Or this can be a choice
Is it ok to hard code our connection string? 1:38:35
got the answer 👍👍
Nice explanation. I was wondering if you could show an example of what should be in the application layer.
stuff like mapping, handling the requests, or even command validation belongs to the application layer,
you can have a look at the final project Repo: github.com/jakubkozera/Restaurants
or follow along rest of the course on udemy
Amazing video. Thank you for sharing.
How did customized your VS to look like this? Really cool!
it's a fluent ui feature from the preview version of VS 17.8+
why watching this video if i can buy the full course thank you so much for this course
thanks for the support :) enjoy the full content
Good tutorial, but is difficult to hear what you are saying
Thank you sir, this is awesome tutorial.