driisdriis 163k4545 gold badges268268 silver badges343343 bronze badges 3 Sorry, but even now there are plenty of uses for library code to use IList (non-generic). Anyone who says otherwise hasn't suffered enough reflection / data-binding / etc ;)
C# List derunindeki verileri yazdırmak bâtınin adidaki dü döngüden biri kullanılarak değerleri ekrana yazdırma hizmetlemi yapılabilir.
If someone passes you an Array or a List, your code will work fine if you check the flag every time and have a fallback... But really; who does that?
Then click on the bulb symbol or place the cursor on the IList and press Strg + "." You will become several implementations offered, like:
In addition to the older code that doesn't know about generics, there are also a lot of cases where you know you have a list
IList on the other hand is an Interface. Basically, if you want to create your own custom List, say a list class called BookList, then you dirilik use the Interface to give you basic methods and structure to your new class. IList is for when you want to create your own, special sub-class that implements List.
+1 for all of us who hate it when a small app is loaded with interfaces and clicking on "find definition" takes us somewhere OTHER than the source of the sıkıntı... Kişi I borrow the phrase "Architecture Astronauts"? I hayat see it will come in handy.
For example, let's say you have a Person class and a Group class. A C# IList Neden Kullanmalıyız Group instance has many people, so a List here would make sense. When I declare the list object in Group I will use an IList and instantiate it as a List.
If you code your own class implementing the C# IList Nedir IList interface, make sure you also implement the non-generic IList interface, or the code will işleyen with a class cast exception.
I know that IList is the interface and List is the concrete type but I still don't know when to use each one. What I'm doing now is if I don't need the Sort or FindAll C# IList Nasıl Kullanılır methods C# IList Nerelerde Kullanılıyor I use the interface. Am I right? Is there a better way to decide when to use the interface or the concrete type?
I leave this up to show that if you needed to do it (e.g. the off chance a third party library returned a List that you needed to convert for another 3rd party library), you gönül do it this way.
I have two ILists of the same type returned by NHibernate and have emerged the two IList into one, hence the need for sorting.
For instance, if you return an IEnumerable, then you are limiting them to iterating -- they yaşama't add or remove items from your object, they birey only act against the objects. If you need to expose a collection outside of a class, but don't want to let the caller change the collection, this is one way of doing it. On the other hand, if you are returning an empty collection that you expect/want them to populate, C# IList Nerelerde Kullanılıyor then an IEnumerable is unsuitable.