It is really a good video sir and clear my idea about indexer.Thank you so much,but what i suggest is please keep variable less. I mean you can keep only eno, ename and salary because with this three variable also your example will be clear.
Why would one access elements by index as it is more error prone. One can easily make typo and application will crash. While using properties one can have advantage of intellisence and all checks will be done at compile time. So where indexer is better option than properties?
I have a query here, for now we have 6 no.of properties so that we can easily unboxing them, but tomorrow if we have more number of properties in the class then what about the performance issue I meant to say by using unboxing... Please let me know.
perfect explanation of indexers thank you sir.
Your rythm of teaching makes even complicated things a lot easier for everyone. Lots of love to you sir :)
Class will behave like a virtual array . using Indexers.. Thanks... very helping sir.
This is the best explanation ever. ❤
It is really a good video sir and clear my idea about indexer.Thank you so much,but what i suggest is please keep variable less. I mean you can keep only eno, ename and salary because with this three variable also your example will be clear.
Thank you, Sir, What a great video!!
Amazing teaching skills
Great sir much useful tutorial tanks
Really Appreciate it ❤️ .
Awesome! Thank you very much sir. Waiting for more from you.
thanks for beautifully explaining the need of indexer.
awesome sir,,,,i got a clear clarity about indexers.
Great 👍👍👍
so perfect the way this is put together. Even the code is large text.
Awesome! Great.. Waiting for more from you. Thank you very much sir.
Thanks sir your videos always helpful for me....!
i love this guy. you are internet end boss.
What an explanation sir thank you 👍🙏
Thanks sir ,You are best teacher
Very helpful...thanks a lot....
you taught this topic very well
Amazing tutorial! Greetings from Poland! :)
Thanks. Now Indexers looks easy to learn.
Excellent Thank you...
loved it
Excellent
Thanks for this valuable video...
great explanation....Thanks Sir
well Explained sir
Thank you sir!
7 years old. Still Excellent Explained.
Tqq sir...for good explanation
Thank you so much, sir. You earned a new subscriber :)
Thanks sir great explanation..
Thank you sir this lecture is very helpful it clear all concepts about indxer
THANK YOU SIR .
Instead of writing chain of if-else in indexer, we can use switch statement of clean, more understandable and less code.
awsome
I have a question sir, at 16:30 u wrote return null; can't i write else Console.WriteLine ("invalid");
since its a get method , it must return something , so its better to return null when the index does not exist
Can we use var instead of object so don't need of type casting
Plz upload video on DbSet and DbQuery classes in EF
Hello sir, plz upload video on reflection and Expression with func delegate
What about adding array to class let's say object[1] refers to array how will we access a particular element in that array
Why would one access elements by index as it is more error prone. One can easily make typo and application will crash. While using properties one can have advantage of intellisence and all checks will be done at compile time. So where indexer is better option than properties?
virtual means? is it runtime creation
I have a query here, for now we have 6 no.of properties so that we can easily unboxing them, but tomorrow if we have more number of properties in the class then what about the performance issue I meant to say by using unboxing... Please let me know.
Do you still have that query?
Salary should be decimal because of it's high precision.
No need to write else if because we are returning from every if
Does it cover entire course
Hello sir, plz upload video on reflection and Expression with func delegate