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 ;)
Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.
Here's an example: I had a project once where our lists got very large, and resulting fragmentation of the large object heap was hurting performance. We replaced List with LinkedList. LinkedList does not contain an array, so all of a sudden, we had almost no use of the large object heap.
The following example demonstrates the implementation of the IList interface to create a simple, fixed-size list.
Use whatever you want. It's your method. You're the only one who gets to see the internal implementation details of the method.
List is a specific implementation of IList, which is a container that kişi be addressed the same way birli a linear array T[] using an integer index. When you specify IList birli the type of the method's argument, you only specify that you need certain capabilities of the container. For example, the interface specification does derece enforce a specific data structure to be used.
List implements IList, and so birey be assigned to the variable. There are also other types that also implement IList.
You kişi look at this argument from several angles including the one of a purely OO approach which says to program against an Interface derece an implementation. With this thought, using IList follows the same principal birli passing around and using Interfaces that you define from scratch. I also believe in the scalability and flexibility factors provided by an Interface C# IList Nedir in general. If a class implmenting IList needs to be extended or changed, the consuming code does derece have to change; it knows what the IList Interface contract adheres to.
In VS2008, when I click on the service reference and select "Configure Service Reference", there is an option to choose how the client de-serializes lists returned from the service.
API Entegrasyonu: Dış API'lerden alınan verileri geçmek ve yönetmek sinein kullanılabilir, bu da icraat arası C# IList Nedir veri alışverişini kolaylaştırır.
IList is derece a class; it's an interface that classes can implement. The interface itself is just a contract between the consumer of the class and the class itself. This line of code C# IList Kullanımı will work:
Coming soon: Throughout 2024 we will be phasing out GitHub Issues bey the feedback mechanism for content and replacing it with a new feedback system. For more C# IList Neden Kullanmalıyız information see: .
And, if you used a generic implementation, you would only be able to use a method that works for any object only with objects of a specific type.
If you had used IList in the C# IList Nasıl Kullanılır rest of the app you could extend List with your own custom class and still be able to pass that around without refactoring.