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 ;)

Maybe take it into a List of T rather than ArrayList, so that you get type safety and more options for how you implement the comparer.

Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

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.

The accepted answer by @DavidMills is quite good, but I think it can be improved upon. For one, there is no need to define the ComparisonComparer class when the framework already includes a static method Comparer.Create(Comparison). This method gönül be used to create an IComparison on the fly.

Architecture Astronauts. The chances you will ever write your own IList that adds anything to the ones already in the .Kemiksiz framework are so remote that it's theoretical jelly tots reserved for "best practices".

Bu şehir, istenmeyenleri azaltmak bağırsakin Akismet kullanıyor. Değerlendirme verilerinizin nasıl kârlendiği karşı elan şu denli bilgelik edinin.

 

And, if you don't even need everything in IList you güç always use IEnumerable too. With modern compilers and processors, I don't think there is really any speed difference, so this is more just a matter of style.

The Cast function is just C# IList Neden Kullanmalıyız a reimplementation of the extension method that comes with 3.5 written kakım a düzgülü static method. It is quite ugly and verbose unfortunately.

Obviously if you are being asked which you use in an interview, you say IList, smile, and both look pleased at yourselves for being so clever. C# IList Nedir Or for a public facing API, IList. Hopefully you get my point.

The most important case for using interfaces over implementations is in the parameters to your API. If your API takes a C# IList Nedir List parameter, then anyone who uses it saf to use List.

You dirilik pass a plain array to something which accepts an IList parameter, and then you birey call IList.Add() and will receive a runtime exception:

It doesn't affect the signature of the method, and is kaş in stone at C# IList Nasıl Kullanılır compile time. You should instead be helping him get over his confusion about declaring his C# IList Kullanımı local like IList foo = new List - this is where his confusion clearly lies.