An interface for what, though?

@@IAmTimCorey Any project can inherit from your teachings. ;)

I like it.

@@mauricemakesmovies not to nitpick right now, but wouldn‘t you implement it, rather than inherit? ;)

@@HDEditzz spot on

I’m glad you liked it.

I'm glad you found it so helpful.

Agreed. Mosh did completely non useful example with unit testing.

@@farfaraway2212 Nice that's really cool. Where?

Lol that's the same thing that happened to me. I still feel like he is a great instructor, and he helped me learn a lot in other areas.

You are welcome

Excellent!

All good...caution pays👍

Same goes for me. Thanks a ton Tim!

I am glad it was helpful.

Thanks for looking to Tim

You are most welcome.

Excellent! I'm glad you found it valuable.

Great!

true.

Great to hear!

Thank you!

You are welcome.

You are most welcome. Thanks for watching.

Awesome! I am glad my content has been so helpful.

Awesome! I am glad it was so helpful.

Awesome!

Thanks for growing your skills and sharing your insights with us.

I appreciate the kind words.

Great to hear!

You are welcome.

Thank you!

Glad to hear it

Thank you!

Glad you enjoy it!

You are welcome.

I am glad it was so helpful.

Have to agree! I never understood the concept of interfaces and abstract classes because it was too complex for me to understand and most explanations i found didn't bring over the message, only examples with animals or cars. Now I got it, thanks to your Videos. I also got a bit more into Async developoing. I appreciate your videos, they do really open a big new field for me.

I am glad it was helpful.

Awesome!

Awesome! I am glad it was helpful.

I am glad it was helpful. Thank you for the kind words.

I am glad you enjoyed them.

I appreciate the kind words.

You are welcome.

Have my like sir

@@nicolasm1664 I hope this was helpful!

Thanks! I added it to the description.

Glad it was helpful!

Awesome!

I am glad you have found my content so valuable.

I'm glad they have been helpful.

You are welcome.

I am glad it was helpful.

Thanks!

Excellent!

Glad it helped!

Thank you for continuing your learning with Tim.

Glad I could help!

haha, nice... love your account name:)

Awesome!

You are most welcome.

Awesome! I'm glad my content has been so helpful.

Wow, thank you!

Thanks!

say did this cover adding the interface to a startup? i seemed to have missed that if it was added.

Great to hear!

Understatement. Like those videos where you can see that they have needed classes in the Solution Explorer but never show you what's in them.

Thanks!

Glad it was helpful!

You are welcome.

I’m glad it was illuminating.

Glad it was helpful! That is why I do this, to make learning easier.

I appreciate the kind words.

You are welcome.

Glad it was helpful!

I'm glad it was clear and helpful. Welcome to the channel.

Thanks!

You are welcome.

I am glad I am so clear to you.

Great to hear!

Sounds good.

wheere do you find 400% playback? I've been trying to do this forever

@@bruceb8140 it's a chrome extension chrome.google.com/webstore/detail/video-speed-controller/nffaoalbilbmmfgbnbgppjihopabppdk?hl=en

Thanks for watching

Awesome! I'm glad things clicked and you were able to see the value in interfaces.

Awesome!

Glad it was helpful!

That’s high praise. Thank you.

Awesome!

They added that since the video was created.

Excellent!

Awesome!

Thank you!

You are most welcome. Thanks for watching.

Great!

Awesome!

Excellent!

I kind of figured out why this example has been bothering me. Technically speaking, IProductModel should actually be IPhysicalProductModel, because it's ShipItem is unique to physical products and therefore should not be a part of the base interface. The base should have something like _void Checkout();_ and IPhysicalProductModel should implement it as ShipProduct() and IDigitalProductModel should implement it as DownloadItem() or somewhere along those lines. This way, the list can have the base class, just call Checkout() on it and each item would call it's defined method. interface IProduct { string name { get; } void Checkout(); } interface IPhysicalProduct : IProduct { void ShipItem() { Debug.Log("Shipping item"); } void IProduct.Checkout() { ShipItem(); } } interface IDigitalProduct : IProduct { int totalDownloadsLeft { get; } void DownloadItem() { Debug.Log($"Downloading item; {totalDownloadsLeft} downloads left"); } void IProduct.Checkout() { DownloadItem(); } } class PhysicalProd : IPhysicalProduct { public string name { get { return "productName"; } } }

Glad it helped!

You are welcome.

Correct.

I do offer sales to my mailing list members and occasionally to the public as a whole once or twice a year. The cost is relative. If you are looking at it compared to a free course or a $10 Udemy course then yes, they are expensive. If you are looking at them in comparison to a college course then they are cheap. My Foundation in C# course series is essentially about 3 semesters worth of teaching (two and a half if you pushed it). Besides, not all training is created equal, just like not every car is the same. Just because a run-down Ford has four wheels and goes when you push the gas doesn't mean that a Mercedes should cost the same because it too has four wheels and goes when you push the gas.

Because he doesn't suck .... And this one video probably saved me 5 hours of spinning....

Thanks for the sub and the endorsement.

Excellent!

Thank you!

Couple of reasons. First, an abstract class implies a relationship (object a "is a" b). That isn't always true. Second, you can only inherit from one class. You can implement multiple interfaces. Here is a quick example: IDisposable. This is an interface created by Microsoft. It has one method definition in it: Dispose(). If you implement that class, you can us a "using" statement to ensure that your class gets disposed of properly. Microsoft does not know about your class, yet you can implement their interface and they can call a method on your class. If you tried to do this with inheritance, you could never inherit from another class if you wanted to be disposable.

Thank you!

Awesome!

It sounds like you are thinking too abstractly. An interface says that a class will have certain attributes. When you use an interface as an object type, you will only have access to those attributes because that is all you know that it has. However, that is a benefit because any class can go into that object, as long as it implements the interface. The IDisposable interface is probably the best example of this. That interface says that a class implementing it will have a Dispose method. That's it. The benefit of having that interface is that we can then apply it to any class we want and know that the class will have a Dispose method. We use this in using statements. For example, we might have this code: using (MyClass test = new MyClass()) { } Now, when the code inside the curly braces completes, the "using" statement will call the Dispose method in our "test" object. How does it know to do that? Because it implements IDisposable (otherwise, we cannot use the using). Microsoft wrote the using statement. They didn't write your code. Yet, Microsoft's code can call your code's Dispose method because it implements an interface Microsoft created. That's why a contract is the most common way of visualizing it. By implementing IDisposable, you are agreeing that you will have a Dispose method. That is the contract you are signing.

Let me state my vision on that (does not mean it is correct, just the way I see it... A property is something like... (3 below) public string Make {get; set;} public string Model { get; set; } public string Year { get; set; } A method is something like... public bool Equals(Car car) { return (this.Make, this.Model, this.Year) == (car.Make, car.Model, car.Year); } A method SIGNATURE is something like... public bool Equals(Car car) (looks like a method without the instructions, just the header...) An interface is a set composed of --some properties and --some method signatures, for example public int xxxx {get;set} public bool yyyy {get,set} public string zzzz (int number) Normally with a name starting with I, say ISomething (but not a must) One may write classes (ex Class CCC) that implement the properties and the methods, witch means it has the same properties and method WITH the "signature" (top line) of the interface. Thats free. (and nobody needs to know) Besides that, if you write "CCC : ISomething" - the name of an interface after the class name, the C# compiler will now you intend to implement the interface ISomething and check for that to help you do it right, and complain if there is some properties or some methods missing... By the way, this is one common thing to do... And what is the use for that? Well one example is the example in the video above... In a nutshell you write code referring to the named interface (ISomething) and that named interfaced is replaced by classes that the compiler knows (you told it) that implements it... ----------------------------- Bur remember, this is only my view of the thing that I dare to show. I hope those that in fact know the subject may correct it... until then...

One more note: I did not know what an interface was until I saw this video, maybe I still do not know...

You are welcome.

I am glad it was helpful.

I am glad it finally clicked!

Awesome! I'm glad I can improve Mondays for you.

Agree, it's the best thing about Mondays ! Thanks Tim!