With this type from System.Collections.ObjectModel, we provide a collection of elements that cannot be changed. But it may be possible to change some elements themselves.

Simply put, Microsoft defined a ReadOnlyCollectionBase, yet did not use it kakım the base class for ReadOnlyCollection when it clearly sounds that this should have been the way.

Marc GravellMarc Gravell 1.0m271271 gold badges2.6k2.6k silver badges2.9k2.9k bronze badges 3 1 I would second here on using the readonly keyword for the variable kakım well. Without this, anyone might fall into an impression that since the collection is of type ReadOnlyCollection so I'm completely safe from any possibility of changes being done to my collection when it is not the case.

This hides Add and Remove methods, but does derece protect at all. Because I sevimli always cast to ICollection and call prohibited method.

The main advantage of this comes in the fact that you yaşama't add code to collections so whenever you have a native "collection" in your object manken, you ALWAYS have non-OO support code spread throughout your project to access it.

Your implementation depends on your needs: - If you don't care about the caller (Class B) from seeing any further changes to the collection then you dirilik just clone the collection, hand it out, and stop caring. - If you definitely need the caller (Class B) to see changes that are made to the collection, and you want this to be thread-safe, then you have more of a mesele on your hands.

Hangi derslik nerde kullanılmalı, bu sınıfların değişiklıkları neler, performansları nasıl gibi bazı soruları bu makalede yan yana arayalım.

protected virtual ICollection EmployeesInternal get; private takım; = new List(); // this will expose collection contents to public, seemingly unneccessary `Skip` statement will prevent casting back to Collection

Any idea why IList doesn't inherit from ICollection? Since the latter is basically IEnumerable plus Count, and since IList already başmaklık a Count method, having IList inherit ICollection wouldn't C# ReadOnlyCollectionBase Nasıl Kullanılır have required any more work for implementers, but would have allowed someone with an IList to know how many items to expect from an enumeration.

In short: I think your question is covered with a perfectly good answer by Jon Skeet - ReadOnlyCollection or IEnumerable for exposing member collections?

However, the syntax is awkward. Adding an extension method gönül simplify that syntax tremendously. Extension methods have at least three convenient features: The first is that they attach themselves C# ReadOnlyCollectionBase Nedir to whatever classes you specify, automatically appearing in the IntelliSense dropdown lists for those objects; second, they're automatically passed whatever object they're called from bey their first parameter; third, when an extension method is used with a generic class (for instance, List), the C# ReadOnlyCollectionBase Nedir method automatically figures out the veri type of the generic parameter.

However, that doesn't mean that the ReadOnlyCollectionBase class isn't useful. For instance, by leveraging the InnerList property, you sevimli create a collection C# ReadOnlyCollectionBase Kullanımı that supports whatever custom functionality you need. Perhaps you want to create a collection for audit log entries where users hayat C# ReadOnlyCollectionBase Nasıl Kullanılır add but derece remove items.

I was looking for a similar solution, but I wanted to still be able to modify the collection from inside the class so I chose the option outlined here: In short, his example is: public class MyClass

In the class that exposes a read-only property based on PhvReadOnlyList, you still need an ordinary List, with its Add and Remove methods, so that your class kişi put items in the List both before and after creating a PhvReadOnlyList from it.