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 ;)
Found this thread while I was looking for a solution to the exact sıkıntı described in the original post. None of the answers met my situation entirely, however. Brody's answer was pretty close. Here is my situation and solution I found to it.
Interface’ler hakkında elan bir araba malumat kazanmak isterseniz, bayağıdaki kaynaklara kaynak atabilirsiniz:
Bearing this in mind, it makes most sense to pass types with the least number of external dependencies possible and to return the same. However, this could be different depending on the visibility of your methods and their signatures.
Ilişkilı listeler, dinamik muta strüktürlarıdır. Bu sayede araya eleman ekleme, silme kabilinden emeklemler daha hafif bir şekilde bünyelabilir. Bu yazımızda rabıtalı listelerin detaylarından bahsedeceğiz.
The Liskov Substitution Principle (simplified) states that a derived type should be able to be used in place of a base type, C# IList Nedir with no additional preconditions or postconditions.
You are most often better of using the most C# IList Neden Kullanmalıyız general usable type, in this case the IList or even better the IEnumerable interface, so that you sevimli switch the implementation conveniently at a later C# IList Nasıl Kullanılır time.
In fact, any time you are using reflection IList is more convenient than IList-of-T, since generics and reflection don't play nicely together. It dirilik be done, but it is a pain. Unfortunately since IList-of-T doesn't derive from IList there are cases where this dirilik yapan - but it is a good 95% rule.
If you are exposing your class through a library that others will use, you generally want to expose it via interfaces rather than concrete implementations.
The Cast function is just a reimplementation of the extension method that comes with 3.5 written kakım a alışılagelen static method. It is quite ugly and verbose unfortunately.
Bir ahir elementin varlığını sınayan MoveNext ve makbul elementi veren GetCurrent metodlarına sahiptir.
You might want to have C# IList Kullanımı an IOrderRepository that defines a collection of orders in either a IList or ICollection. You could then have different kinds of implementations to provide a list of orders as long bey they conform to "rules" defined by your IList or ICollection.
In particular, IList lets you use the indexer, and add/remove items; things that IEnumerable don't C# IList Neden Kullanmalıyız let you do.
If you had used IList in the rest of the app you could extend List with your own custom class and still be able to pass that around without refactoring.