The following example demonstrates the implementation of the IList interface to create a simple, fixed-size list. This code is part of a larger example for the IList interface.

C# CollectionBase dershaneı, özelleştirilebilir koleksiyonların oluşturulmasını katkısızlar ve bu sayede nominalm projelerinde elastikiyet ve tekrar kullanılabilirlik esenlar.

Edit: You do need to be quick to get answers in here. Birli I presented a slightly different syntax to the other answers, I will leave my answer - however, the other answers presented are equally valid.

So when writing a function or method that takes a collection, write it hamiş to take a List, but an IList, an ICollection, or IEnumerable. The generic interfaces will still work even for heterogenous lists because System.

This will allow me to do generic processing on almost any array in the .NET framework, unless it uses IEnumerable and not IList, which happens sometimes.

The Liskov Substitution Principle (simplified) states that a derived type should be able to be used in place of a base type, with no additional preconditions or postconditions.

Most app-level code (i.e. the everyday code that ou write for your application) should probably focus on the generic versions; however there is also a lot of infrastructure code around that must use reflection.

In fact, any time you are using reflection IList is more convenient than IList-of-T, since generics and reflection don't play nicely together. It güç be done, but it is a pain. Unfortunately since IList-of-T doesn't derive from IList C# IList Nerelerde Kullanılıyor there are cases where this birey yapan - but it is a good 95% rule.

For example, let's say you have a Person class and a Group class. A Group instance has many people, so a List C# IList Kullanımı here would make sense. When I declare the list object in Group I will use an IList and instantiate it kakım a List.

Then later if you decide to convert the actual data store from a List to a Dictionary and expose the dictionary keys as C# IList Nasıl Kullanılır the actual value for the property (I have had to do exactly this before). Then consumers who have come to expect that their changes will be reflected inside of your class will no longer have C# IList Neden Kullanmalıyız that capability. That's a big problem! If you expose the List bey an IEnumerable you yaşama comfortably predict that your collection is not being modified externally. That is one of the powers of exposing List as any of the above interfaces.

 

Returning a read-only interface such birli IEnumerable is often the way to go for veri-retrieval methods. Your consumer sevimli project it into a richer type bey-needed.

I have two ILists of the same type returned by NHibernate and have emerged the two IList into one, hence the need for sorting.

Fakat list kullanmaında kapasite belirtilmez kullanıcak veriler sınırlı ise örneğin haftanın günleri ise bunları diziye teşhismlayabiliriz ancak kullanılacak veriler makine plakası,telefon numarası üzere adetsı muamma veriler kullanıcak ise mutlaka C# IList Neden Kullanmalıyız list olarak saklanmalıdır.Şimdi C#’ta list tasarrufı sinein örneğimize bakalım.