C# IList Kullanımı Ile ilgili detaylı notlar

C# IList Kullanımı Ile ilgili detaylı notlar

Blog Article

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 / data-binding / etc ;)

Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.

Using IList instead of List makes writing unit tests significantly easier. It allows you to use a 'Mocking' library to pass and return veri.

It's more nuanced than that. If you are returning an IList kakım part of the public interface to your library, you leave yourself interesting options to perhaps make a custom list in the future.

In this specific case since you're essentially talking about a language construct, hamiş a custom one it generally won't matter, but say for example that you found List didn't support something you needed.

You gönül have an instance of an interface, but you need to initialize it with a class that implements that interface such birli:

Most app-level 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.

Now I am returning IList for the simple fact that I will then add this to my domain biçim what katışıksız a property like this:

For example, let's say C# IList Nasıl Kullanılır you have a Person class and a Group class. A Group instance saf many people, so a List here would make sense. When I declare the list object in Group I will use an IList and instantiate it bey a List.

List implements those ebe methods C# IList Neden Kullanmalıyız (hamiş including extension methods), on tamamen of that it saf about 41 public methods, which weighs in your consideration of which one to use in your application.

This argument only works if C# IList Neden Kullanmalıyız you write your own implementation of IList from sratch (or at least without inheriting List)

Şimdi bu arada bir örnek yapalım. Bir C# IList Nasıl Kullanılır bir numara yönlü ilgilı liste oluşturalım ve bu listeye değme olarak eleman ekleyelim. Bu eklediğimiz elemanları C# IList Kullanımı da ekrana yazdıralım:

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ü everything you need.

The other general reason for using interfaces is to expose the minimum amount of knowledge necessary to the user of an object. Consider the (contrived) case where I have a data object that implements IList.