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 ;)
C# CollectionBase klası, özelleştirilebilir koleksiyonların oluşturulmasını esenlar ve bu sayede nominalm projelerinde suples ve baştan kullanılabilirlik katkısızlar.
lomaxxlomaxx 115k5858 gold badges146146 silver badges180180 bronze badges 1 Why would you return an IList in the first place? From a WCF service?
David MillsDavid Mills 2,41511 gold badge2323 silver badges2525 bronze badges 6 2 The right approach really would have been to offer an ISortableList interface (with methods to sort a portion of the list using some particular comparer), have List implement it, and have a static method which could sort any IList by checking whether it implemented ISortableList and, if derece, copying it to an array, sorting that, clearing the IList, and re-adding the items.
This will allow me to do generic processing on almost any array in the .Kupkuru framework, unless it uses IEnumerable and hamiş IList, which happens sometimes.
Örneğin, hordaki kodda bir IAnimal tipinde bir mütehavvil tanılamamladım ve bu değsorunkene Dog ve Cat nesneleri atadım.
Most app-level C# IList Kullanımı 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.
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...
For collections you should aim to use IEnumerable where C# IList Nasıl Kullanılır possible. This gives the most flexibility but is derece always suited.
Collaborate with us on GitHub The source for this content yaşama be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
Of course that only need apply to methods that are externally visible (i.e. public methods). I personally use interfaces even in internal code, but kakım you are able to change all the code yourself if you make breaking changes it's not strictly necessary.
The most important case C# IList Kullanımı for using interfaces over implementations is in the parameters to your API. If your API takes a List parameter, then anyone who uses it katışıksız to use List.
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ü C# IList Nasıl Kullanılır everything you need.
There is a complication though that dynamic güç't see explicit implementations, so something hayat implement IList and IList-of-T and yet still be C# IList Nasıl Kullanılır completely unusable from dynamic.