C# IList Nasıl Kullanılır Herkes İçin Eğlenceli Olabilir

C# IList Nasıl Kullanılır Herkes İçin Eğlenceli Olabilir

Blog Article

It's always best to use the lowest base type possible. This gives the implementer of your interface, or consumer of your method, the opportunity to use whatever they like behind the scenes.

Bir dahaki sefere yorum yaptığımda kullanılmak üzere adımı, e-posta adresimi ve web şehir adresimi bu tarayıcıya kaydet.

Koleksiyonlar, verileri belirli bir düzende depolamak ve yönetmek ciğerin kullanılan data binalarıdır. CollectionBase ile kendi koleksiyonlarınızı oluştururken, bu muta binalarını elan hareketli ve gür bir şekilde kullanabilirsiniz.

All concepts are basically stated in most of the answers above regarding why use interface over concrete implementations.

Typically, a good approach is to use IList in your public facing API (when appropriate, and list semantics are needed), and then List internally to implement the API. This allows you to change to a different implementation of IList without breaking code that uses your class.

Örneğin, aşağıdaki kodda bir IAnimal tipinde bir kararsız tanılamamladım ve bu bileğmeselekene Dog ve Cat nesneleri atadım.

class Kisi string ad; string soyad; public string Ad get return ad; kaş ad = value; public string Soyad get return soyad; grup soyad = value;

Don't you know in advance if your method needs a list that kişi take additional members; don't you specify that in the method signature? What exactly were you going to do if you were passed a read only list like int[]?

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

If you emanet consider your method, determine that you probably won't be changing the return collection type, then it is probably safe to return a more exact type. If you aren't sure, or are afraid that if you change it in future you'll be breaking other C# IList Nasıl Kullanılır people's code, then go more general.

It is like this other question. The other question shares a lot of common ground, but is arguably hamiş a true duplicate. In either case though, this is not opinion-based. What may have happened is that the closer might have just C# IList Nerelerde Kullanılıyor looked at this question's title, without reading the question itself. The body is objective.

In this case you C# IList Nerelerde Kullanılıyor could pass in any class which implements the IList interface. If you used List instead, only a List instance could be passed in.

You emanet pass a plain array C# IList Nerelerde Kullanılıyor to something which accepts an IList parameter, and then you güç call IList.Add() and will receive a runtime exception:

For instance, if you return an IEnumerable, then you are limiting them to iterating -- they güç't add or remove items from your object, they kişi only act against the objects. If you need to expose a collection outside of a class, but don't want to let the caller change the collection, this is one way of doing it. On the other hand, if you are returning an empty collection that you expect/want them to populate, then an IEnumerable is unsuitable.