Yes, of course. Just use HttpClient as you would in any other consumer app.

You are welcome, I am glad you found the video helpful.

Thanks, glad you liked it!

You are very welcome, and thank you for watching the video. Regarding your question, to be 100% honest, for me, Factory pattern is a pattern that strongly depends on abstraction, whether it is one version or another. The way you see it in the video is something I've used in my projects earlier, but I am pretty sure Factory Method could be implemented as well, just I would need to sit down and go through the solution again. After all both patterns are quite similar so I see no reason why you couldn't use the Factory Method instead.

@@CodeMaze thanks for your answer again, amazing work ;)

I appreciate the kind words! Thank you too for watching the video.

Thank you. I believe you think about the HttpClientFactoryService class. The HttpClientFactory just happened to be already registered there, and I used the same class to show how we can use the typed client.

You are very welcome. Thank you too for watching the video.

@@CodeMaze ❤

Hi. I am not a mobile developer, and didn't work with mobile apps, so I am not sure how tokens are stored there. Again, because I didn't work with mobile app development, I can't say for sure how things are working there. You can definitelly consume the API with your mobile app, just I can't tell you how tokens are handled there.

Hi. Thank you for watching the video. It is a class with some constants.

Fron .NET 8, Microsoft integrated Identity support, and there they provided all the endpoints for the authentication, refresh etc. For me, it is not ready yet for the full production usage because it is not that much customisable. Therefore, for me, using my own implementation is still way to go.

Thank you for the kind words and for watching the video. No, all the courses are on our courses page. You can find the link in the description.

Hi. AddIdentity registered a few more services than AddIdentityCore. If you don't need Role services or SignInManager services, you can use the Core version.

There is nothing much to say there - you have a serious security issue then. This simply shouldn't happen. But if you have a client app, and you store your tokens in some sort of storage, you can encrypt them in the client app first and then store them. That way, if someone steals them, the tokens will be of no value to them. Of course, you have to remember to decrypt them before using them in the request.

Thank you! I am glad you found the video helpful.

You can send an email to any provider. Once you prepared your server to send your emails from, you can use the app to send those emails to any email address.

@@CodeMazewill it work just by following everything in the video or need additional configuration need not shown on video also what happens from @4:44 to @4:55 it change from namespace .Services to .Model why?

No, you don't need any additional configuration. You only need to setup your server that you will use to send your emails from. Other than that, everything is in the video. Here I didn't setup Gmail as the server because it would require a lot more configuration but I linked the video where I use Gmail to send emails so you can watch that one. Regarding the second question - namespace is not changed, just the using directive was added because I am using an object from different namespace.

Glad it was helpful! Thank you too for watching it.

You are welcome. Thank you for watching.

My pleasure! Thank you for watching the video.

I am glad the video helped you. Yeah, this has to be configured in a certain place in the middleware's hierarchy.

No, I didn't want to include Gmail here because it is a bit harder to set it up with all the GMail restrictions and app passwords. But, as I said in the video, I have another one where I use MailKit library with Gmail, you can find it linked in the description.

I am glad the video was helpful. I am trying to help as much as I can. Thank you for the membership and watching the video.

Glad to hear it! Thank you for watching the video.

Hi. That's great to hear. I am sure I can't answer all the questions in a single video, but if it can help you or anyone else with their search and further learning, I am more than happy with it :)

@@CodeMaze that is exactly what you did, thank you kindly!

You're welcome! Thank you for watching the video.

Glad it was helpful!

I would always go with a centralized place to handle excpetions, without try-catch blocks in each action separately. Then, if you need some complex logic, you can customize your handler, extract classes with the logic, etc, but still, the base handling logic is in a single place. It reduces the code complexity in your actions and your business logic.

What is wrong with try catch anyway i dont get it I think this structure way more complicated for me yes u defines as ones but you eventually sending each exception same type of objects and 500 for all of them not a good idea in my opinion. İnstead of this I created genericresponsebase class and define error,notfound,success etc methods inside of it and whenever program catches the exception I pass arguments into error func all details and finally when the request finish I return IAction functions such as ok,notfound,badrequest etc.

And I want to understand something that what is differences between localy control and globally, is there any performance differences or just dry opinion clean arc behind of it

Hi. First of all, there is nothing wrong with try catch blocks, just having them in every action or every method is not the cleanest approach. Now, regarding your comment about 500 error all the time, in one part of the video I state this: "One thing to mention here. We are using the 500 status code for all the responses from the exception middleware, and that is something we believe should be done. After all, we are handling exceptions and these exceptions should be marked with a 500 status code. But this doesn't have to be the case all the time. For example, if you have a service layer and you want to propagate responses from the service methods as custom exceptions and catch them inside the global exception handler, you may want to choose a more appropriate status code for the response. You can watch about this technique in the Onion Architecture video, which you can find in the description below." So, I have the Onion Architecture video where this technique is used to return different status codes to the client. Everything you see in the global exception handler can be customized and extracted into own classes, if needed, so for me, this is always a cleaner approach - the way I use in all my projects. Also, I don't think there are any performance advantages for this approach, at least, not that I have noticed, but reagarding the cleaner actions and cleaner service layer methods - that's for sure.

​@@CodeMazethanks for the response great explanation

:), I need to try harder, I guess :) Thank you for watching the video. Glad it was helpful.

I always used filters. The logic inside them are reusable and all we have to do is to add the filter on top of action. I am not sure about middleware and how you can do that there. I would like to see an example of that one.

Thank you! Cheers!

Glad the video was helpful! Thank you for watching it.

Hi. Thanks a lot for the kind words and for watching the video. Yes, you have to use the await keyword because the second async call depends on the result of the first one. So, you have to wait the first one to be completed and return the required result.

await/async ultimate goal is to free the Threads (send the Threads back to the ThreadPool) so it can process other Tasks. If a baker just wait for a cake to be baked in the oven, it would be inefficient, right? Instead, he could go and do some other stuff while waiting for the cake. Same with Threads, with external services, like Database calls (Cloud Database), or Cloud Storage Service (AWS, Azure), your Threads do not need to resolve these, it's the external service Threads' jobs. If you don't release YOUR Threads by using await/async, the Threads will wait and do nothing, and Threads are really limited. So, await/async does not make your functions faster, but rather utilize the resource (Threads).

Great recapitulation of my video, thanks for that.

Thank you for watching the video. I didn't set the address. MassTransit knows it by default via configuration.

You are welcome

If you talk about the ProcessorResolver delegeate, it should be string as the value of the PrcessorResolverKeys class has all the constants of the string type.

Thanks so much for your response, yeah, I did not see you show the content of ProcessorResolverKeys class, I thought that it is a Enum Then I use Enum type so the first approach can run successfull but for the AddKeyedTransient case, it fail because the key should be string. Again, really aprreciate your video

Try using the same library version I used. These things change so fast - therefore they might have changed something.

No special reason, I just didn't need it here, and I can get the body from the request as shown in the video.

Glad you think so! Thank you for watching.

Hi. It is an online text course. You can do it at your own pace. The platform allows a lot better reading and learning experience and that's why we decided to move from PDFs to online courses.

I can't say for sure, but I'll have it in my mind.

To be honest, never tried that. It was usually one UI one API :)

Glad you enjoyed it! Thank you for watching the video.