IEnumerable interface

IEnumerable interface

1. IEnumerable and IEnumerator in C#

Many junior C# developers find the two IEnumerable and IEnumerator interfaces confusing. In fact, I was one of them when I first started learning C#! So, in this post, I’m going to explore these two interfaces in detail.

2. IEnumerable Interface

Exposes an enumerator, which supports a simple iteration over a non-generic collection.

3. IEnumerator Interface

Supports a simple iteration over a non-generic collection.

4. IEnumerable <T> Interface

IEnumerable <T> Interface

5. IEnumerable Examples

Use the IEnumerable interface. IEnumerable things can be looped over with foreach.

6. IEnumerable in C#

Many times there is a need to loop through a collection of classes or lists which are anonymous types. IEnumerable interface is one of the best features of C# language which loops over the collection. Let us learn about it step by step so beginners also can understand.

7. Can anyone explain IEnumerable and IEnumerator to me? [

Can anyone explain IEnumerable and IEnumerator to me?
For example, when to use it over foreach? what's the difference between IEnumerable and IEnumerator? Why do we need to use it?

8. IEnumerable and IEnumerator in C#

Most novice C# programmers find it difficult to understand the difference between IEnumerable and IEnumerator. In this C# programming tutorial, we will explain what these two interfaces are and what their significance is in C# programming and software development.

9. Difference between IEnumerable and List

The main difference between IEnumerable and List in C# is that IEnumerable is an interface, while List is a concrete class. Moreover, IEnumerable is read-only and List is not. List represents the entire collection in memory, while IEnumerable provides an interface for getting the next item one-by-one (enumerating data).

10. IEnumerable in C#

In this article, we are going to learn about IEnumerable in C#. IEnumerable acts as an abstraction over a collection and allows us to iterate over it without knowing the actual type of the collection.

11. C# Pitfalls of returning IEnumerable

It is often preferred to work with as generic types as possible. Doing that opens up for more flexibility and being able to modify parts of the code without effecting any other parts. One example of this is IEnumerable which is implemented by several generic collection types, such as HashSet, List, and LinkedList.

12. Best Practices Implementing the IEnumerable Interface

IEnumerable is one of the most prominent interfaces shipped with the .NET Framework. Nevertheless, in practice we constantly encounter less desired implementations of this interface. In this article we will cover the origin, the purpose, and best practices in implementing IEnumerable interface in C#.

13. Everything You Wanted to Know About IEnumerable Single-Item Searches (But Were Afraid to Ask)

I often read code in forums or Stack Overflow from people who are beginners at C#, and see them using FirstOrDefault in every situation where they need a single item from an IEnumerable. If I ask them why they made this choice, the reply is typically something like “it always works” or “it gets the job done.” This is often not true. The problem with this logic is that it doesn’t consider the data model, and in many cases may be flat-out ignoring it. The .NET IEnumerable interface has several options for when you just want one specific item from the collection, and if you consider all of the options you have for getting a single item from an IEnumerable, it forces you to think about your data model. Here are the basic options: