Interface in C#

[@dnfvideo]

30 Important C# Interview Questions : kzbin.info/www/bejne/eHzcn3h4hdacf68 25 Important ASP.NET Interview Questions : kzbin.info/www/bejne/ponQfpejf7p2Zsk 25 Angular Interview Questions : kzbin.info/www/bejne/Y5vIoKx6f6mmia8 20+ SQL Server Interview Questions : kzbin.info/www/bejne/iXbHcnluorh-iZY 5 MSBI Interview Questions : kzbin.info/www/bejne/a3abYmiXjaaqj7M

[@adityaghosalkar431]

One of the best explanation I have ever seen about Interfaces Thank You so much

[@250miles2]

This has to be the absolutely best video I've seen on interfaces. No contest. Every video has failed to show how code reuse actually happens and, really, how "multiple inheritance" occurs, when usingan interface. For me, the missing link was the Factory design pattern... I've watched this video about 4 times now, and every time I watch it, I pick up something new. Thank you for creating this!! Truly amazing work.

[@swingymcswing]

Now that I've heard this, I feel like I understand more than before. Didn't really realize there were implicit contracts and that multiple interfaces can happen after app is in production to add new features and not break existing interfaces. Very nice explanation.

[@pickle1987]

From my point of view, Interfaces are used mainly to implement Polymorhpisme, they are very useful to decouple your code base (if you are using an IoC framework) by injecting the interface representing your concrete Presenter/Service or whatever you want, and lastly if you write unit tests with Microsoft Fakes you will need them to generate your stubs

[@dnfvideo]

Polymorphism exists because of parent child relationship. With out inheritance there is no polymorphism.I an create a parent simple base class and still do DI for child classes. Decoupling is a product of polymorphism. Polymorphism gives the ability to run objects differently under different conditions and thus hiding the concreteness. With simple base class i can still do plymorphism and DI.I do agree interfaces gives you a very generic structure as compared to simple class where you will have some base implementation. SimpleClass x = new SimpleChildClass1(); x.Method1(); x = new SimpleChildClass2(); x.Method1();

[@markanthonysabado9632]

Real world scenario we use Interface because of polymorphism and swappable component.

[@jonathansaindon788]

@@dnfvideo parent child relationship has more to do with inheritance than polymorphism. Interfaces are the simplest and cleanest way of achieving polymorphism.

[@rohityadav5802]

The First Time I could understand the actual use of the interface, Excellent explanation thank you very much for this video.

[@MichaelRainabbaRichardson]

Great video as others have said! I needed it as a bit of a refresher and at the end I wonder if others might appreciate another perspective on interfaces. I look at the interface as a declaration of what my class should be while the class is the implementation of that design. Contract is incredibly appropriate when looking at it from the perspective of consumption, but if you are developing from a purely OOP perspective, interfaces represent the abstract of how an object should present itself ("what") while the class describes the actual solution ("how"). In these examples, the interfaces were extracted from the class, but from a design perspective, you would logically define your entities, then build your interfaces to start solidifying the design, then you would begin to build your classes using those interfaces as schema/blueprint/outline to create actual behaviors.

[@AmitKumar-mt9mf]

One of the best explanation of Interface over the internet. Thanks you so much for creating this video.

[@adapass]

Awesome explanation of interface. I have never seen any article in google explaining the need of interfaces like this in a clear very simple way. Even a programmer with a very little knowledge on c# or oops can understand this. You are rocking. Please keep posting c# videos like this.

[@CyberAbyss007]

Thank you for this video. Just took a live online class last week so its sort of fresh in my head. It took me a bit to get it. Interfaces are like server side include templates but when we say contract just means the class template is enforced from a signature perspective. You don't put any code in the interface so its only useful depending on the circumstances. If you have a large code base with lots of classes with similar functionality then use interfaces so you can enforce class signatures and modify them as needed and if you want to consume less info than is in the base class. Again, thanks for the video. Creating classes as abstract all you designate classes as optional (can be overridden) in the using class using the override keyword.

[@Imrankhan-nn5kp]

The Best video over the internet on interface. Thank you so much . It helped a lot.. keep going brother.

[@manishjawarkar84]

Best explanation for Interface and Clear all my doubts. Thank you so much.

[@FeroChau]

In my perspective, an interface is mainly used for achieving flexible object composition which is one of the core concept in Elements of Reusable Object-Oriented Software. Also, I think the primary benefit of an explicit contract is that it could provide loose coupling, flexibility and interchangeability of the implementation methods. It could also reduce the compile time but I don't think it is the main reason of using an interface.

[@kopilkaiser8991]

Thank you for the video. I am watching it from London. I have learnt a great deal about C# interfaces.

[@gauravvijaygupta6240]

It is my first time when i watch your video and it is my best experience now i will watch more video on different topic.

[@tonygoyal5781]

One of the best explanation on any topic ,i have ever seen. Thanx alot sir..

[@MrBivanovs]

The best description about subject

[@HeathInHeath]

Thank you for this video. I found your explanation and discussion to be very helpful in building my awareness of which situations would benefit from adding the abstractions of interfaces or the factory pattern.

[@bachelorcookingandeating1918]

One of the best examplaction on the interface. This is the right way to use interface in real development Thank you so much sir ... For grate session

[@fredmassey1062]

The best explanation I have found for understanding interfaces, and why they are used. Thank you.

[@marziehfatemi7615]

Thanks for this video. I think the most important usage of the interface is for dip, Ioc and interface segregation rules of solid. and this happens when we create multiple layers when one layer needs another and we want to decouple them to loosely coupling.

[@rohityadav5802]

Best video on the interface over youtube

[@adapass]

Awesome explanation for even experienced programmers with very simple sample program.

[@PankajChauhan-jx1ie]

I have so much doubt on interfaces...because if they only contains signatures then why we can't use these methods direct from class...but i really appreciate the concept of caller and callee.....it clears my all doubts regarding interfaces..thankyou so much..

[@srikplaylist]

It looked like greek language before watching this video, now it looks so simple. Thanks a TON!!!

[@salmanahmad2532]

20:01: Correction: Interfaces contain only method declaration and not the definition. This means by default all the methods in an interface are the abstract method and public. Great explanation.

[@salmanahmad2532]

@.NET Interview Preparation videos

[@nisargshah5485]

I have seen lots of videos regarding this topic,but this is a best explaination ever about interface 💯

[@abhishekr8021]

Thanks very much for making me understanding interfaces uses in realtime.

[@Sunstriderko]

definitely the best video about interfaces out there. Thanks for amazing job

[@avinashgoyal8243]

Best video for Interface I ahve ever seen!!

[@hansdevelde6326]

Thanks for this very clear explanation !

[@vsrrawat7954]

Great explanation.....i like it very much....Thank you for this

[@manjitsarma6592]

This is it(end of all confusions surrounding Interface)..Awesome video.Thanks !!

[@kiransaravade5127]

great explanation .. shiv sir u cleared my wrong assumption about interfaces

[@emmadkareem5247]

Thanks for your efforts. I see that removing the factory and dynamic concepts would have made your point much clearer.

[@balamurugankalyanasundaram426]

Nice article about the interfaces. I have few questions. 1.Instead of Factory pattern, we can choose any other patterns like abstract factory or resolver or DI? 2.Will abstract class solve the same problem discussed here? if it so, what are the other advantages to prefer interfaces? 3.Can we use abstract classes for dependency injection?

[@sistemamarco]

Finally a good explanation. Good job.

[@umerwaqas5943]

That was just amazing opinion sir. Nicely explained.

[@SeanSmith73]

Superb presentation - thank you.

[@renzybi5061]

Best explanation of this topic! And ive seen alot. You have a knack for teaching brother! Many thanks

[@yousufanwer99]

Best Explanation ever ,Please make video on polymorphism

[@selvaa5876]

Really very good explanation about Interface. great session. Thank you so much !!!

[@VikasKumar-jk5yh]

Explained very well and elegantly..

[@navidkh1883]

This is an awesome video. 👌 thanks very much.

[@Hehe-k6j]

Prasad Sir, Its great video and very good, clear and clarity explanations. Really, all my doubts are cleared regarding interface. Great Job, Thanks.

[@NirajTiwariYoutube]

Best explanations- first time I have learn about interface in actual

[@ranadheera7574]

This is real tutorial, superb.

[@fooballers7883]

Thank you for a very detail explanation about interfaces...

[@faisalkhanjalalia1966]

Great explanation! However it would be a cherry on top if you could discuss about access modifiers while implementing interfaces.

[@JohnStephen7]

A great explanation about interfaces and its benefits. Thank You so much

[@soomon3608]

Thank you so much for this video. I think I finally understood what interfaces are used for!

[@TellaTrix]

Such superb explanation sir, We usually used interface for decoupled entity, but there has lot of things that we could use with interface.

[@learnwithmoonlight4463]

Thank you so much for such nice explanation!!

[@tauseefahmed2680]

the best example and explanation I found here about the interface , thank you :)

[@huntervanguard6423]

Helped greatly with my understanding of how interfaces are to be used. Thanks a lot.

[@harishpoojary9183]

Very clear presentation on interface. Thank you.

[@Ahmet-nd5ct]

Great explanation.thnls

[@samadhanphad5683]

This is the great explanation on interface I ever seen , thanks for the video.

[@sarathbaiju6040]

Great video. Interface is also helpful for unit testing

[@husamdarwish7009]

Thank you so much Very clean and clear explanation Keep explaining mind defusing ideas in C#

[@jithinm5692]

Thank you for the clear explanation

[@amithaacharya]

what a video!! Just loved it.

[@ankurkamthan5854]

Cleared many doubts today

[@ba1h1dinesh]

Very nicely explained

[@yogeshnainwal8319]

it ' too good explanation about interface.

[@satish123mattaparti]

Thank you best explanation, now i can feel the use the interface

[@nishanthgmk3487]

Awesome explanation, can you make a video about Startup.cs, DI, constructor injection, overriding, etc. Your videos are the best to understand. Thanks for the great video

[@aagebadho6907]

Adding to all the points, Interfaces are required for dependency Injection ( which also helps us to do Unit Testing)

[@nkp107]

thanks sir, I think now no need to read more about interfaces. Everything is clear now.

[@geirO2]

Good work, explains it very well...

[@KDOERAK]

A great video: clear explanation, good examples! thx

[@sanjaikhola7184]

Nice video very good explanation about Interface help for me a lot.

[@PushpendraKumar-hy5pd]

Love this videos ! Nice explanation of Interfaces.

[@sukhjinderpawar]

Best explanation so far

[@dgowtham5290]

Your teaching way is awesome.

[@tusharkantidas4622]

best explanation on interface I've ever read... Thank u Shiv :)

[@meenubatra6283]

Such a nice explanation of interface.Sir can you make a video on abstract class vs interface because abstract class can do whatever interface can do except multiple inheritance.

[@AkashKumar-kc5cp]

Thank You so much.

[@vinokarthik99]

Thank you so much... You made it very clear

[@hemantkumartalasu9398]

Very good explanation.

[@achilleskocaeli]

Respect. After that video, I learnt interfaces. I am now immortal.

[@hakrman2954]

no u r not

[@davsx6201]

Ooh great!! one of the best videos about interfaces

[@balamuruganp3865]

Excellent excellent , after watching this completely understand about interface, feeling great and confident on this. Thank you sir.

[@yogeshwargoswami]

Really help me to understand the interface..... What exactly the interface is.

[@RollinShultz]

It does seem like Interfaces are great for separating concerns and also implementig methods not defined in the base class. I suppose they are mostly used to coommunicated view to viewModel etc. If I want to make a small application that's specific to a type of person, so using you maths model, let's say I want to use a math class for an application that calculates volumme of concrete to order for a job. I have the basic math class with +,-,*,/ methods, and an interface that implements the advanced maths for calculus and trig functions, and for my contractor who doesn't have any use for those advanced features, I make an interface for concrete calculating methods for volume, and square footage etc. which are relevant to the contractor application. It certainly makes the maths class smaller and eliminates the bloat which would be caused by including unneeded advanced methods. Maybe it utilizes a mobile phone UI so we want to keep the phone app small. However, we want the phone app to be part of a greater application product. Interfaces then would be better than multiple applications all from scratch.

[@THILLAIRAJA24]

Great explanation thanks sir...

[@mohaithi]

very good explanation about interface. Now I understood Interface when and where to use. Thanks a lot shiv!!

[@manojsawant186]

Best explanation so far....

[@mrchali-rl8es]

great explanation. Thank you so much for sharing

[@malayaprasadlenka9088]

Awesome 👍

[@learningislife2934]

Great sir

[@maxmanila1]

super explanation

[@sanketnaik2825]

Hi sir, Can you please make a practical video on SOLID properties....

[@dotnetchapter]

Awesome shiv sir. Thanks a lot..

[@renganathane8185]

I agree with your words.

[@yashshah1497]

The great explanation I have ever seen for an interface. Appreciated :)

[@shashikantrajak1784]

Even if you are using implicit conectarte you should use interface for mock testing and other purpose.

[@11223a3b]

Thank you 😊

[@learningislife2934]

I am big fan sir

[@ZiaurRahmanAdvocate]

Good presentation. I would also like to see a discussion on more than 4-5 interfaces working together with some Database connectivity examples. May be a real life case can be reviewed as well.