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.
Then the person calling the method is free to call it with any data 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 derece too hard to create a couple of methods that will allow you to sort an IList birli you would a List.
So when writing a function or method that takes a collection, write it derece to take a List, but an IList, an ICollection, or IEnumerable. The generic interfaces will still work even for heterogenous lists because System.
Use whatever you want. It's your method. You're the only one who gets to see the internal implementation details of the method.
I would turn the question around a bit, instead of justifying why you should use the interface over the concrete implementation, try to justify why you would use the concrete implementation rather than the interface. If you güç't justify it, use the interface.
The cost to do this is minimal, why derece save yourself the headache later? It's what the interface principle is all about.
Now I am returning IList for the simple fact that I will then add this to my domain benzer what özgü a property like this:
Bir dahaki sefere tefsir yaptığımda kullanılmak üzere hamleı, e-posta adresimi ve web şehir adresimi bu tarayıcıevet kaydet.
If you code your own class implementing the IList interface, make sure you also implement the non-generic IList interface, or the code C# IList Kullanımı will yapan 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 methods I use the interface. Am I right? Is there a better way to decide when to use the interface or the concrete type?
Then I looked in my view(mvc) and found that I actually C# IList Nedir needed the count method kakım I needed to use a for loop. So in my own application I under estimated what I actually needed how C# IList Neden Kullanmalıyız do you anticipate what someone else will need or derece need.
Unless you have a very compelling reason C# IList Nedir to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it katışıksız everything you C# IList Nasıl Kullanılır need.
This works, because only the outer list is created in the first place. You sevimli then insert individual items that are compatible with IList: