DEPENDENCY INJECTION in ASP.NET Core | Getting Started With ASP.NET Core Series

What is difference between services.AddTransient<DependencyService1>(); and services.AddTransient<DependencyService1, DependencyService1>();
Behind scene what is happening how its registering Single Class or Linking <Interface/Abstract,Class> object in Dependency Injection and behind the scene how it allowing and disallowing object life time

Thank you for including a book recommendation for those who want to take a deep dive - I'm always looking for recommendations on resources and people are hesitant to make recommendations they don't personally directly benefit from

Very Precise, Simple and easy to understand .. really liked it.

nice

Great Tutorials and awesome channel thanks Rahul it helps me a lot

FYI, Startup.cs is missing because it got merged into the Program.cs file. Hope that helps someone!

You're great teacher, greetings from Poland :)

Good job, detailed explanation which helps in realtime development.

Hi Rahul, how can we Inject parameterized constructor using dependency injection?

Hello Rahul, I eally appreciate your clear explanation but have a question: After override IFunctionsHostBuilder at startup; When I call azure function from client side with url and appkey then function fails with error message like this: Microsoft.AspNetCore.Authentication.Core: No authentication handlers are registered. Did you forget to call AddAuthentication().Add[SomeAuthHandler]("WebJobsAuthLevel",...)?. Please help me know how the way to fix this trouble.

I've no words to explain how good You explain a Complicated concept this much Easily, your channel is going to be very big in the future, All the best Sir. Love from INDIA ♥♥♥.

I appreciate this video but man do I hate how .net does this stuff. My eyes glaze over at all this ServiceProvider, ServiceCollection, IOperation... stuff. I hate it so much lol

Please post the video for SOLID principles with the real time scenarios implementation

Specifically Open/Closed and Liskov Substitution Principle

Nice job. You're a great explainer.

Thank you :)

Could you please explain the scenarios when should use Azure Web Jobs Vs Azure Functions Vs Logic Apps
and need the scenario to use Azure Service bus Queues and Topics

Please advise.

Good explanation Thanks Rahul.

I like that you covered small details while explaining a concept. --- Give this man a raise (Obama pointing finger).

Thanks for the video, i have a question, say i have a class library without any startups.cs or program.cs , is it possible to implement dependency injection without startup.cs or program.cs ?

Thanks for clear explanation

Why we use Interfaces for dependency injection or repository patten? is there any other way to achieve this ?

This is great!

Thanks 😎

Thank you for great videos Rahul !

This is just amazing, thank you very much!

Thanks again for good explanation

Love the way you explain.....

very good explications , thanks

Thanks Rahul. This was great.

Pure Gold Content. Thanks a lot man for all of the great content you make.

Ah man, I have to ruin the 420 like count because you deserve one more like. Great video!

I really appreciate your work. Thank you so much for sharing your knowledge. I am currently using Visual Studio 2022. Lot of things changed, there is no startup.cs. Would it be possible to update your videos for Visual Studio 2022 ?

why I did not found you earlier. Making my interview preparation easy with each video. Great explanation not just this video but all.

This is a gem...

nice explanation Rahul, i really liked the diagram showing the lifetimes

now i can start

The best. I really really appreciate your clear explanation. I'm sure this channel is going to get much bigger. Thank you

You are awsome sir! You are fucking Awsome!

You explain so well. I'm glad I stumbled upon your channel. Keep it up.

awesome

Every request to the controller will result in creation of new DependencyService1 and DependencyService2 objects because they are registered as Transient. However within the DependencyService1/2 code you have used various types of IOperations (registered as transient/scoped/singleton). In the case of scoped and singleton, how does the program ensure that within every new instance of DependencyService1/2 you get same instance of scoped (in the single request) and same instance of singleton (across all requests)? Is this the functionality of the DI container's internal implementation? Also, is this an example of multilevel DI that you have shown? Level 1 is the DependencyService1/2 and Level 2 is the Operation.

Awesome sir👍

Great video 👍

Amazing work, so far it's the best explanation for Dependency Injection.

You are amazing man. No one else explained this in easy and understandable way