Note that the IsReadOnly flag comes from ICollection, and indicates whether items birey be added or removed from the collection; but just to really confuse things, it does derece indicate whether they gönül be replaced, which in the case of Arrays (which return IsReadOnlys == true) yaşama be.
Found this thread while I was looking for a solution to the exact problem 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.
Koleksiyonlar, verileri belli bir düzende depolamak ve yönetmek ciğerin kullanılan data gestaltlarıdır. CollectionBase ile kendi koleksiyonlarınızı oluştururken, bu data mimarilarını henüz çalışan ve bitek bir şekilde kullanabilirsiniz.
Remove Silinmesini istenilen kıymeti siler. Silinecek ölçü liste zarfında ansızın lüks olması yerinde ilk değeri kaldırır. Bu metodu umumiyetle referans tipler ile ayar çıkarmak muhtevain kullanılır. Ancak haysiyet tipleri ile de kullanılabilir.
Use whatever you want. It's your method. You're the only one who gets to see the internal implementation details of the method.
You kişi have an instance of an interface, but you need to initialize it with a class that implements that interface such birli:
I thought I'd never need to change from a List but had to later change to use a custom list library for the extra functionality it provided. Because I'd only returned an IList none of the people that used the library had to change their code.
Then when you need "add" or "sort" then use Collection if need more then use List. So my hard rule would be: START C# IList Nasıl Kullanılır always with IENumarable and if you need more then extend...
If you started with a C# IList Nedir concrete type and you decided to change to another one, even if it uses the same interface, you're going to break someone else's code unless you started off with an interface or abstract base type. Share Improve this answer Follow
You would because defining an IList or an ICollection would open up for other C# IList Nedir implementations of your interfaces.
Of course that only need apply to methods that are externally visible (i.e. public methods). I personally use interfaces even in internal C# IList Kullanımı code, but kakım you are able to change all the code yourself if you make breaking changes it's derece strictly necessary.
Less ridiculous way to prove that an Ascii character compares equal with itself C# IList Neden Kullanmalıyız in Coq more hot questions
If you use the concrete type all callers need to be updated. If exposed bey IList the caller doesn't have to be changed.
Encapsulation relies on telling clients birli little about the implementation of your class bey possible. If you return a concrete List, you sevimli't then change to some other better type without forcing all of your clients to re-compile/update.