Видео

Very nice explanation thank you

very good explanation Sir

Why .net core?

January 2023 and still AMAZING. WOW

Great practical introduction. Traversing backwards would have been nice to show as well. Thank you for putting this video together.

Thank you for a very good and simple explanation

Hello, What about using Return for If (Game.IsLoading) { return; } so if the game is loading, it return to block the flow to conitnue to read the code, since the Game.IsLoading() So we have to wait the end of the Game.IsLoading to continue to read the Script. is it working like that?

It would have been great if you could've elaborated on calling methods that add the cargo to the LL

Whew thanks for this. Tried studying this from a book I've been using to learn C# and their example and explanation was so much more complex. This was great, appreciate you taking the time to share!

There is no difference in output with or without callback? So what's really happening? Is it just theory to understand that using delegate, our compiler will be doing other tasks rather than just waiting for a task to complete?

I think if you could explain Interfaces and why they are used it would help with your overall introduction of dependency injection. Dependency Injection is a very complex topic that involves a lot of other concepts which makes using DI powerful that deserve to be touched on so that people can have a really good understanding and use of DI rather than just illustrating the mechanics of the code. Its just not a 15 minute video and we owe more to developers that are trying to learn how to apply this new powerful design pattern that inplements IoC. We owe them more than this. The best way I can explain it would be that using an Interface along with DI you are creating a paradigm that allows objects to directly talk to each other.

Why the delegate needs to be public since it is not being called directly from outside of the class?

Well explained

good tutorial, but I still don't see the advantage of this pattern, can you elaborate?

Why did you copy and paste almost every little chunk? Makes the video go by slowly when typing it could be much faster.

posting the compiled script in case anyone needs it: using System; namespace myPrivateAccessModifierProj { class Program { static void Main(string[] args) { //new instance of myNames myNames n = new myNames(); string inName = n.GetName; Console.WriteLine(inName); Console.ReadKey(); } } class myNames { private string name = "Joe"; //the public function access the private var ^^ public string GetName { get { return name; } } } }

My notes from the video below: using System; using System.Collections.Generic; namespace myIndexerProj { class Program { static void Main(string[] args) { myAnimals myAnimalList = new myAnimals(); Console.WriteLine(myAnimalList[4].AnimalType + " Type"); Console.ReadKey(); } } public class Animal { public string AnimalType { get; set; } public int Legs { get; set; } } //class to hold the list to index w indexer public class myAnimals { private List<Animal> Animals = new List<Animal>(); //add constructor public myAnimals() { Animals.Add(new Animal { AnimalType = "cat", Legs = 4 }); Animals.Add(new Animal { AnimalType = "bird", Legs = 2 }); } //indexer public Animal this[string inAnimal] { get { foreach (Animal a in Animals) if (a.AnimalType.Equals(inAnimal)) return a; return null; } } public Animal this[int inAnimal] { get { foreach (Animal a in Animals) if (a.Legs.Equals(inAnimal)) return a; return null; } } } }

great example of how to use generics... I added both string and int for testing: using System; namespace myGenericClassProj { class Program { static void Main(string[] args) { myMatchCheck<int> myIntObj1 = new myMatchCheck<int>(); myMatchCheck<string> myStringObj1 = new myMatchCheck<string>(); Console.WriteLine(myIntObj1.myMatchWasFound1(4, 4)); Console.WriteLine(myStringObj1.myMatchWasFound1("cow", "cat")); Console.ReadKey(); } } //<> means generic class myMatchCheck<myData> { public bool myMatchWasFound1(myData Val1, myData Val2) { if (Val1.Equals(Val2)) return true; else return false; } public bool myMatchWasFound2(myData Val1, myData Val2) { if (Val1.Equals(Val2)) return true; else return false; } }

I feel like Neo in the Matrix, now I know basic Json.

great video

amazingly simple, yet effective explanation

very good explanation, easy to understand - please make more videos

cool

Theen , Thanks to my day , since i went through the tutorial , which helped me to understand the constructor injection so clearly

where's my capital letters?

This has been the best explanation I've seen (and I've watched like 10) so thank you and well done!

Great Explanation!!!!🙏

This is the best explanation I have seen for DI, keep it up.

there is a callback in any delegate using begininvoke() which will also make the function run in different thread never the less You did a great work thank you

Thank you for the video.Finally I understood DI.Thanks for sharing !!

"The confusion gives you great benefit" - that saved my day :-) - Thx.

Thank you preparing this video for us.

I now understand. Thank you kindly.

thanks for the video. one thing, people who look for this king of subjects - know basic things like open new project or console.read....

Thanks. Please make more videos like this......

Good tutorial, but no need to F5 to check syntax. It is done automatically by Visual Studio as you type.

I really wasn't getting how delegates and callbacks worked but your video was simple and easy to understand. Thank you!

so what' s beauty of delegate based callback rather than calling function?