I know there saf been a lot of posts on this but it still confuses me why should you pass in an interface like IList and return an interface like IList back instead of the concrete list.

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

Say I have a function that returns IEnumerable, inside the function I may use a List for an internal backing store to generate my collection, but I only want callers to enumerate it's contents, derece add or remove. Accepting an interface bey a parameter communicates a similar message "I need a collection of strings, don't worry though, I won't change it."

Then click on the bulb symbol or place the cursor on the IList and press Strg + "." You will become several implementations offered, like:

This will allow me to do generic processing on almost any array in the .Kemiksiz framework, unless it uses IEnumerable and derece IList, which happens sometimes.

Convert your IList into List or some other generic collection and then you emanet easily query/sort it using System.Linq C# IList Nasıl Kullanılır namespace (it will supply bunch of extension methods)

You may hamiş ever need that option, but it's an argument. I think it's the entire argument for returning the interface instead of the concrete type. It's worth mentioning, but in this case it has a serious flaw.

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:

In VS2008, when I click on the service reference and select "Configure Service Reference", there is an C# IList Nedir option to choose how the client de-serializes lists returned from the service.

List implements those nene methods (not including extension methods), on top of that it başmaklık about 41 public methods, which weighs in your consideration of which one to use in your application.

Bayağıdaki şekilde Kisi isminde oluşturduğumuz sınıfı oluşturduğumuz liste nesnesine ekleyelim.

I leave C# IList Nerelerde Kullanılıyor this up to show that if you needed to do it (e.g. the off chance a third party library returned a List that C# IList Neden Kullanmalıyız you needed to convert for another 3rd party library), you birey do it this way.

List klası teşhismlanırken T tip değmaslahatkenini allıkır. şu demek C# IList Kullanımı oluyor ki listenin muhteviyatında ne türden nesne yada değişçilikkenlerin olacağını belirler.

would I run into problems with this? Since could they not pass in an array(that has a fixed size)? Would it be better maybe for a concrete List?