วีดีโอ

Thank you 🙌

Thank you, Azzam! 🙏

Thank you for the feedback Shahnawaz! 🙏

Thank you for sharing this, I’m glad I was able to help 🙏

yep, i would choose this

Interesting approach yeah

OH DAMN! I didn't see that, stupid auto caption 😅 (And you can f-ire)

In my other video on background services, I showed how to do that with fixed timer, CRON was planned to be part of that video but it got too big for a simple video. Probably I should revisit that in a separate one! Nice one!

Thank you 🙏

You can automate versioning with SemVer and commit messages, and set up automation in CI/CD pipelines using feature branches for revision/preview versions. However, manually changing versions following the semantic versioning (major.minor.patch) is important to avoid breaking changes

@@mdbouk any plans for a video on this?

Yes, sounds like a good idea, I will put it in the queue 🙌

JetBrains Rider

Thank you 🙌

The Journal is an automatically created SQL table inside your database. It records the name of the file and the time of deployment. As for your ‘smart’ guy, he shouldn’t update existing scripts 😅The best rollback strategy is to roll forward, by creating new script to update what is needed

I really appreciate that 🙏 thank you 🫡

Thank you 🙏 I appreciate it

True, pushing the same version won’t overwrite it. Instead, create a ‘dev’ version with a random prefix, e.g., 1.0.1-patch1. You can automate versioning with SemVer and commit messages in CI/CD pipelines. However, manually changing versions using semantic versioning (major.minor.patch) is important to avoid breaking changes

Absolutely! The client, which could be your web application, should handle tenant resolution through the JWT. In real-life scenarios, you send the tenant in the JWT and perform some validation. If the tenant is changed in the header, you validate that the logged-in user has access to the provided tenant or fall back to the user’s default tenant. For simplicity, I showed it as part of the header, this approach simplifies the process and demonstrates resolving custom services from tenant configurations. I thought I made this clear in the video

@@mdbouk I did understand, but I also think that this type of info should be mentioned in the video. Some junior dev is going to not know about this and just implement as demonstrated.

You are right, I will make sure to cover this in a dedicated video to provide a clearer explanation. Thank you for pointing that out!

Glad you liked it! Thanks 🙏

Thank you for your feedback, Scott! Appreciate you sharing your approach. My take on that, it depends on the context and the situation. After all, if we are doing unit tests, we should mock all other dependencies and focus on the test in hand

Glad you liked it 🙏 hopefully it wasn’t too late 😅

Thanks ✌️

Glad you enjoyed it 🙏

😂 I’m glad to hear that!

You are correct. My intention was to showcase PLINQ, but you are right that it might not be ideal for background services. However, PLINQ can still be useful for certain scenarios where you need to handle cancellation and exceptions in a more defined way. Thank you for pointing that out!

@@mdbouk .NET 9 introduces Task.WhenEach() for less straightforward asynchronous cases. Could be an interesting topic for a followup video regarding more indepth discussions regarding async/parallel, async enumerables, etc...

It is indeed an interesting topic. I will wait for .NET 9 to come out before making any videos, just to avoid any future changes 😅

Ouch, you are correct!

Yeah, I missed saying that! The reason is that you can now inject any scoped service into your action class (efcontext, repository, ..)

Thanks! Which part of the discussion did you find most insightful?

Thank you 🙏

If it is an API request, you can inject IHttpContextAccessor and get the requestAborted cancellationToken. Var cancellationToken = httpContextAccessor?.HttpContext?.RequestAborted ?? CancellationToken.None; But to have more control and flexibility, pass the cancellationToken and manage it accordingly

Thank you!

Thanks 👀

🕺

😁

Consider this, you are working with unit tests, you create one faker and every time you need a random user you can call the generate. Or: you are working with APIs, your implementation is not yet complete so you want to return some fake (but realistic) users, you create the faker and return one or multiple. The beauty of it is that you configure the faker once and every time you want a new fake instance you generate

Thank you Tamer! Appreciated 🙏

I just found it! thank you for your content.

Good to know 😁 it is an interesting package

@mdbouk I emailed you but I haven't heard from you! Did you get my email. Thanks

Strange, I didn’t get that

Thanks for the feedback! It sounds like a great topic, Let me see what I can do. Stay tuned!

Thank you Joy