Support Me: / angelsix Part of the series of tutorials on programming C# for beginners Understand what interfaces are, how we create them and when and why we use them
Recently started to learn Csharp and couldnt understand why people use interfaces.. everything makes sense now! You present everything so well its easy to understand, its a shame I have only found your channel now and not earlier! Its full of good content! Subscribe and Like! Thanks
Thank you so much for taking your time to produce cool and useful tutorials videos for us....God bless you for that...I have learnt so much from all your c# videos...Thanks for that....keep the good work going....I hope in the future, you will find time to do videos on Entity framework....
can you show an example of using an existing interface like IComparable to implement comparing some straight forward examples like - ints, strings, then maybe some custom types? I am interested in the last one because I assume you will have to define the bool operators (==, =)?
I would love to see video about difference between interfaces like IEnumerable,IEnumerator,IQueryable and IList. Why we need them? Why we couldn't use array and list instead all of this interfaces? You are great, I admire and appreciate your work.
I have one observation to tell: region with private fields you name as "Private Members", but the term "members of the class", includes fields, events, methods, etc.
Isn't casting here means polymorphism also abstract can be used like this way. but in inheritance from abstract to class or from class to another class we can't inherit more than one class (in c#) only java can do it.
In unit testing, should i test implementation or interface? if second, how to pull of DI from another project to the unit test one to get the current implementation? whats the best approach for this case?
Testing typically tests the actual implementations. You cannot test and interface as such. You can test against an interface, but an interface needs an implementation to do anything. You would unit test each implementation of everything, and you would unit test the entire application too by constructing the application (injecting all services to DI) and then running specific tests on them too.
please, if possible, try to stick to one serie at time, working on multiple series results in one video each one to two months for each, that's too much time.
I do this in my spare time while running my businesses. Unfortunately it's not that simple. Every other series is easy to do, as I either have to do no prep work (or very little) or its much faster to edit etc... The Fasetto Word is the main series and will remain that way, but that takes a lot of time that I don't have right now. It takes over 8 hours (so a full day) to prep each video, then half a day of recording, writing the description, commiting code, creating screenshots, uploading etc... and thats if nothing goes wrong. The Word app doesn't follow anything I am currently doing in work or business so I have to use all my spare time to produce those videos. Only 800 people of 23,000 subscribers even watch them, and I basically have to lose my entire weeks worth of spare time with family to produce a single video in that series. I am well aware of peoples desire that that series is priority (and it is) but behind the scenes, even though it looks like I'm doing loads of series, that simply because they are much quicker to produce when I have less time.
Being able to share your valuable knowledge in your spare time is an absolutely awesome gift to us. I am sure I am not the only one to think this but the whole course has been extremely valuable course. On one hand I hope that you shall get some free time soon to produce some of the awesome WPF/ASP.Net videos however on the other hand it sounds like your business is very busy at the moment and I wish you the best of luck! :)
Thanks so much for the hard work you put in. I know, it's difficult, especially fassetto word and the wpf part, it needs preparation, we like all your videos, but we can't hide the fact that we are more interested in fasette word serie than anything else.
What is your thought of having a marker interface? An interface without any members. By the way thanks for all the hard work brother. Really appreciate it.
Yeah people use them as needed, to flag a class inside an assembly, typically just for loading plug-in style apps or for post-IL processing like Fody Weaver does
All good, just went insanely busy as soon as I released a product to market. I've got a video coming out tomorrow and then I'm at CES on business for next week so video will be out then a few weeks from now
A very helpfull lecture in the main. However: Don't waste time typing comments. Your giving a Lecture with a throw away example. no one will ever read them and it unnecessarily wastes the viewers time. Write a script. Stream of consciousness Lectures have their place, but listening to you constantly correct yourself is very irritating. Reposition your Mic, so that we don't have listen to the incessant clatter of your keyboard. It's almost drowning you out at times and distracts from what you are saying. You cant get rid of keyboard noise altogether and it would sound odd if you did, but it should be far back in the background. Slow down your delivery a little. It will make listening to your lectures more pleasant and easier to follow. Please accept these comments as constructive. No unpleasantness has been intended.
First thank you for your work. I hate to say it, but watching almost all of your Videos, It gets really annoying watching you typing so fast and also talking fast. Also, writing comments is great I love it, but not necessarily for every tutorial. Sorry, don't be angry, just saying my opinion! Best regards
Thats ok. I am actually talking slower than normal here haha. I'll try to talk even slower in my new videos. For commenting, thats my style. Unique but very important for good code in my opinion. Thanks for the feedback :)
