I know there özgü been a lot of posts on this but it still confuses me why should you pass in an interface like IList and return an interface like IList back instead of the concrete list.
Then the person calling the method is free to call it with any veri type that is enumerable. This allows your code to be used in unexpected, but perfectly valid ways.
I think that, ideally, the .NET Framework would include a static sorting method that accepts an IList, but the next best thing is to create your own extension method. It's not too hard to create a couple of methods that will allow you to sort an IList birli you would a List.
A List object allows you to create a list, add things to it, remove it, update it, index into it and etc. List is used whenever you just want a generic list where you specify object type in it and that's it.
Demetlı listeler, devimsel done bünyelarıdır. Bu sayede araya eleman ekleme, silme kabilinden konulemler henüz amelî bir şekilde konstrüksiyonlabilir. Bu ovamızda bağlı listelerin bilgilerindan bahsedeceğiz.
then, say, if you had an array and wished to print their type names to the console, you would first have to create a new List and fill it with your types.
I thought I'd never need to change from a List but had to later C# IList Nerelerde Kullanılıyor change to use a custom list library for the extra functionality it provided. Because I'd only returned an IList C# IList Nasıl Kullanılır none of the people that used the library had to change their code.
From my reading I think I could C# IList Neden Kullanmalıyız have used IEnumberable instead of IList since I am just looping through stuff.
If you are exposing your class through a library that others will use, you generally want to expose it via interfaces rather than concrete implementations.
tranmqtranmq 15.5k33 gold badges3232 silver badges2727 bronze badges 6 But in this case I hayat't bind my collection to DataGridView rather I have to expose the _list member in MyCollection.
This argument only works if you write your own implementation of IList from sratch (or at least without inheriting List)
This is usually guaranteed for a specific implementation of a container (List documentation: "It implements the IList generic interface using an array whose size is dynamically increased birli required.").
Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since C# IList Neden Kullanmalıyız it saf everything you need.
IEnumerable allows you to iterate through a collection. ICollection builds on this and also allows for adding and removing items. IList also allows for accessing and modifying them at a specific index. By exposing the one that you expect your consumer to work with, you are free to change your implementation. List happens to implement all three of those interfaces. If you expose your property birli a List or even an IList when all you want your consumer to have is the ability to iterate through the collection. Then they could come to depend on the fact that they hayat C# IList Neden Kullanmalıyız modify the list.