2:50 what do you mean when you say if there is some change in class B then it's gonna impact class A ? If i make a change in class B then it's normal for class A to feel that change no ? otherwise why i make the difference in class B if i don't want class A to be affected in some way ? Or the word impact means changing code in class A ? Do you mean if there is some change in class B , then you will need to change code in class A ? Because the word impact can have many interpretations , which one is true ?
Hi @exe.m1dnight, Your last statement is correct. As developers, we are responsible for reducing dependency as much as possible. If there is a change in class B, then we need to prepare our class A in such a way that either no or minimal modification is required in class A.
I already covered an example in this video via LogToText and LotToSQLDB Class. Here in this case, if you add a parameter in Class B constructor you have to change your class A and to all similar classes that are referencing Class B. But if you are using DIP or DI, there will be only one place in your project where you take the responsibility for object creation. In that case, you only need to make modifications only in one class, not in all the classes that are referencing Class B. What if you don't want to use Class B altogether? There is a different team or Vendor who created class C for you which is more efficient. Then in all referenced classes, you have to create an object of Class C.
Hi SENATHIPATHI, Glad to know you want to see more videos from this channel. I will definitely try to create videos on this topic as well. As I am not a professional TH-camr and only creating videos in my free time, it might take some time 🙂
@@ProConcepts Really you look like professional youtuber... With in a short term you got very good viewer.... You will get very good returns... I will support always from Bangalore 👍
Hi Nitesh, With IOC, the general idea is to give responsibility to someone who can handle it better than the current implementation. When we create a class library, the main purpose is either reusability or separation of concern. If I hardcode connection string in my class library (.dll) project, it will be tightly coupled with my DLL project. Which we certainly don't want. We want whosoever using my DLL can set their own connection string (or any other properties) as per their needs. So, If you are using DLL within your web project you can consider yourself one of the clients of that DLL. And you can define connection string in your web.config file, instead of the DLL owner hardcode connection string in their project.
2:50 what do you mean when you say if there is some change in class B then it's gonna impact class A ? If i make a change in class B then it's normal for class A to feel that change no ? otherwise why i make the difference in class B if i don't want class A to be affected in some way ? Or the word impact means changing code in class A ? Do you mean if there is some change in class B , then you will need to change code in class A ? Because the word impact can have many interpretations , which one is true ?
Hi @exe.m1dnight,
Your last statement is correct. As developers, we are responsible for reducing dependency as much as possible. If there is a change in class B, then we need to prepare our class A in such a way that either no or minimal modification is required in class A.
@@ProConcepts how can class B change and affect class A? Can you give me examples?
I already covered an example in this video via LogToText and LotToSQLDB Class.
Here in this case, if you add a parameter in Class B constructor you have to change your class A and to all similar classes that are referencing Class B. But if you are using DIP or DI, there will be only one place in your project where you take the responsibility for object creation. In that case, you only need to make modifications only in one class, not in all the classes that are referencing Class B.
What if you don't want to use Class B altogether? There is a different team or Vendor who created class C for you which is more efficient. Then in all referenced classes, you have to create an object of Class C.
Excellent video
Thanks Pranesh, for your positive feedback 😊
This is by far the best video in this topic.
Glad to know you think this way. Thanks for your positive feedback 😊
Good comparison ❤
Glad you like our content. Thank you for visiting our channel.
Nicely explained, thanks for making this video... looking forward for design patterns videos.
Most welcome 😊
Perfect thanks it was too helpful for me, your way is too simple for the IOC & DI. Again thanks a lot
Glad it helped!
Amit, can you upload Design patterns??
Hi SENATHIPATHI,
Glad to know you want to see more videos from this channel. I will definitely try to create videos on this topic as well.
As I am not a professional TH-camr and only creating videos in my free time, it might take some time 🙂
@@ProConcepts Really you look like professional youtuber... With in a short term you got very good viewer.... You will get very good returns... I will support always from Bangalore 👍
Sir plz config file did not get plz
Hi Nitesh,
With IOC, the general idea is to give responsibility to someone who can handle it better than the current implementation.
When we create a class library, the main purpose is either reusability or separation of concern. If I hardcode connection string in my class library (.dll) project, it will be tightly coupled with my DLL project. Which we certainly don't want. We want whosoever using my DLL can set their own connection string (or any other properties) as per their needs.
So, If you are using DLL within your web project you can consider yourself one of the clients of that DLL. And you can define connection string in your web.config file, instead of the DLL owner hardcode connection string in their project.
@@ProConcepts Thanks sir..