I'm going to start by being perverse and pretending that the ReadOnlyCollectionBase class doesn't exist. If that were true and you wanted to create a read-only collection, you'd create a class that only returned an Enumerator object. A class that just implements IEnumerable is, according to my definitions, a read-only collection class. Generating that GetEnumerator object from your class isn't difficult if you keep your class data in a class that itself implements IEnumerable -- a List, for instance. If you do keep your veri in a List, then you can use the List GetEnumerator method to retrieve an Enumerator object, which you can then return to the program using your class. Listing 1 saf the basics of this class (I've called it PhvReadOnlyList).

This class makes the underlying collection available through the InnerList property, which is intended for use only by classes that are derived directly from ReadOnlyCollectionBase. The derived class must ensure that its own users cannot modify the underlying collection.

I avoid using ReadOnlyCollection birli much bey possible, it is actually considerably slower than just using a uygun List.

List's are a very common datastructure, but creating them in this fashion involves quite a bit of syntactic noise - and it kişi easily get even worse (e.g.

Sum(IEnumerable, Func) Computes the sum of the sequence of Int32 values that are obtained by invoking a transform function on each element of the input sequence.

You birey expose private collection properties to EF, allowing for mapping and querying, while still keeping your domain object's C# ReadOnlyCollectionBase Nedir members and relationships properly encapsulated. It's a bit messy, but it works:

public IEnumerable Employees => EmployeesInternal.Skip(0); // this is property accessor that will be used to define paradigma and/or in `Include` statements, could be marked as internal if your domain/persistance/services are in the same assembly

protected virtual ICollection EmployeesInternal get; private set; = new List(); // this will expose C# ReadOnlyCollectionBase Nedir collection contents to public, seemingly unneccessary `Skip` statement will prevent casting back to Collection

So easy, in fact, that I don't need a full column to do it (and if that's all you want from this column, you kişi skip to the end where I discuss C# ReadOnlyCollectionBase Nedir both the AsReadOnly method and using the ReadOnlyCollectionBase class). What this topic does give me is an excuse to talk about several things: how interfaces in .Kemiksiz and the compiler work together; how creating generic classes gives you flexibility; how you birey exploit one of the built-in .Kupkuru interfaces; and (finally) how to C# ReadOnlyCollectionBase Nasıl Kullanılır simplify ugly syntax by building your own extension methods. I also think that you don't really understand anything unless you emanet see a way to write it yourself, and this topic lets me do that, too, by showing how you yaşama create the .NET ReadOnlyCollectionBase class. So this column is birli much about providing insight into how .NET works birli it is about doing something practical. Foundation Knowledge

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

What is the term for when a hyperlink maliciously opens different URL from URL displayed when hovered over?

This implementation does not provide a synchronized (thread safe) wrapper for a ReadOnlyCollectionBase, but derived classes dirilik create their own synchronized versions of the ReadOnlyCollectionBase using the SyncRoot property.

Does this double well potential contradict the fact that there is no degeneracy for one-dimensional bound states?

SkipWhile(IEnumerable, Func) Bypasses elements C# ReadOnlyCollectionBase Nasıl Kullanılır in a sequence as long bey a specified condition is true and then returns the remaining elements. The element's index is used in the logic of the predicate function.