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 / veri-binding / etc ;)
IList is an interface so you birey inherit another class and still implement IList while inheriting List prevents you to do so.
Bu şehir, istenmeyenleri azaltmak bâtınin Akismet kullanıyor. Yorum verilerinizin nasıl işlendiği için daha lüks veri edinin.
Eric LippertEric Lippert 656k182182 gold badges1.3k1.3k silver badges2.1k2.1k bronze badges 14 12 How do you know what the caller needs though. For instance I was switching one of my return types to a IList then I well I am probably just going to enumerate over them anyways lets just return an IEnumberable.
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
GitHub'da bizimle işbirliği strüktürn Bu içeriğin kaynağı GitHub'da bulunabilir; burada başkaca problemlerı ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Henüz zait malumat bâtınin katkıda bulunan kılavuzumuzu C# IList Nasıl Kullanılır inceleyin.
Dizilerde C# IList Nerelerde Kullanılıyor evetğu kadar özellikle kaç adet elemanla çhileışılacağı belirtilmek zorunda değildir. Dizilerde olduğu üzere eleman ekleme, silme çalışmalemleri uygulanabilir ve araya eleman eklenebilir. Ilişkilı listeler sağlamladığı avantajlardan dolayı daha çok tercih edilir.
Then when you need "add" or "sort" then use Collection if need more then use List. So my hard rule would be: START always with IENumarable and if you need more then extend...
The idea is that you hide the implementation details from the user, and instead provide them with a stable interface. This is to reduce dependency on details that might change in the future.
Why does the Clausius inequality involve a single term/integral if we consider a body interacting with multiple heat sources/sinks?
However, this makes the method more fragile, bey any change to the C# IList Nedir returned object type may break the calling code. In practice though, that generally isn't a major sorun.
Then I looked in my view(mvc) and found that I actually needed the count method as I needed to use a for loop. So in my own application I under estimated what I actually needed how do you C# IList Neden Kullanmalıyız anticipate what someone else will need or hamiş need.
Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it özgü everything you need.
If you had used IList in the rest of the app you could extend List C# IList Neden Kullanmalıyız with your own custom class and still be able to pass that around without refactoring.