Why LINQ depends on extension methods in C Sharp (C#) - See It in Action

Why LINQ depends on extension methods

📖 Scenario: Imagine you have a list of numbers and you want to find all the even numbers easily. LINQ helps you do this in a simple way. Behind the scenes, LINQ uses something called extension methods to add new abilities to lists without changing their original code.

🎯 Goal: You will create a list of numbers, add an extension method to find even numbers, and then use it to get and print those even numbers.

📋 What You'll Learn

Create a list of integers called numbers with values 1, 2, 3, 4, 5, 6

Create a static class called MyExtensions with an extension method GetEvenNumbers for IEnumerable<int>

Use the extension method GetEvenNumbers on the numbers list to get even numbers

Print the even numbers separated by spaces

💡 Why This Matters

🌍 Real World

Extension methods let developers add useful features to existing classes without changing their code. This is how LINQ works to query collections easily.

💼 Career

Understanding extension methods is important for writing clean, reusable C# code and working with LINQ, which is widely used in software development.

1

Create the list of numbers

Create a list of integers called numbers with these exact values: 1, 2, 3, 4, 5, 6

C Sharp (C#)

# Create the list of numbers
// Your code here

Hint

Use List<int> and initialize it with the values inside curly braces.

2

Create the extension method

Create a static class called MyExtensions and inside it create a public static extension method called GetEvenNumbers that takes this IEnumerable<int> source and returns only even numbers using a foreach loop and yield return

C Sharp (C#)

using System.Collections.Generic;

List numbers = new List { 1, 2, 3, 4, 5, 6 };

// Create static class MyExtensions with extension method GetEvenNumbers
// Your code here

Hint

Extension methods must be inside a static class and have this before the first parameter.

3

Use the extension method to get even numbers

Create a variable called evenNumbers and set it to the result of calling numbers.GetEvenNumbers()

C Sharp (C#)

using System.Collections.Generic;

List numbers = new List { 1, 2, 3, 4, 5, 6 };

public static class MyExtensions
{
    public static IEnumerable GetEvenNumbers(this IEnumerable source)
    {
        foreach (int number in source)
        {
            if (number % 2 == 0)
            {
                yield return number;
            }
        }
    }
}

// Use the extension method to get even numbers
// Your code here

Hint

Call the extension method directly on the numbers list.

4

Print the even numbers

Use a foreach loop to print each number in evenNumbers separated by spaces on one line

C Sharp (C#)

using System.Collections.Generic;

List numbers = new List { 1, 2, 3, 4, 5, 6 };

public static class MyExtensions
{
    public static IEnumerable GetEvenNumbers(this IEnumerable source)
    {
        foreach (int number in source)
        {
            if (number % 2 == 0)
            {
                yield return number;
            }
        }
    }
}

IEnumerable evenNumbers = numbers.GetEvenNumbers();

// Print the even numbers separated by spaces
// Your code here

Hint

Use Console.Write inside the loop to print numbers on the same line separated by spaces.

Practice

1. Why does LINQ in C# rely on extension methods?

easy

A. To add query capabilities to existing types without modifying them

B. To create new classes for each query operation

C. To replace all existing methods in a class

D. To make the code run faster by compiling queries separately

Solution

1. Step 1: Understand LINQ's design goal

   LINQ aims to add query features to existing collections without changing their original code.

2. Step 2: Role of extension methods

   Extension methods allow adding new methods to existing types externally, enabling LINQ queries without modifying those types.

3. Final Answer:

   To add query capabilities to existing types without modifying them -> Option A

4. Quick Check:

   LINQ uses extension methods to extend types [OK]

Hint: Extension methods add features without changing original classes [OK]

Common Mistakes:

• Thinking LINQ creates new classes for queries
• Believing extension methods replace existing methods
• Assuming LINQ compiles queries separately for speed

2. Which of the following is the correct syntax to define an extension method used by LINQ?

easy

A. public int Sum(this IEnumerable<int> source) { ... }

B. public static int Sum(this IEnumerable<int> source) { ... }

C. public static int Sum(IEnumerable<int> source) { ... }

D. public int Sum(IEnumerable<int> source) { ... }

Solution

1. Step 1: Identify extension method syntax

   An extension method must be static and have the first parameter preceded by 'this' keyword.

2. Step 2: Check each option

   public static int Sum(this IEnumerable<int> source) { ... } is static and uses 'this' on the first parameter, correct for extension methods.

3. Final Answer:

   public static int Sum(this IEnumerable<int> source) { ... } -> Option B

4. Quick Check:

   Extension method = static + 'this' parameter [OK]

Hint: Extension methods are static with 'this' on first parameter [OK]

Common Mistakes:

• Omitting 'static' keyword
• Missing 'this' keyword on first parameter
• Making method non-static

3. What will be the output of this code snippet?

var numbers = new List<int> {1, 2, 3};
var result = numbers.Where(n => n > 1).Count();
Console.WriteLine(result);

medium

A. 3

B. 0

C. 1

D. 2

Solution

1. Step 1: Understand the Where clause

   It filters numbers greater than 1, so it keeps 2 and 3.

2. Step 2: Count the filtered elements

   There are 2 elements (2 and 3), so Count() returns 2.

3. Final Answer:

   2 -> Option D

4. Quick Check:

   Filtered count = 2 [OK]

Hint: Count filtered items after Where condition [OK]

Common Mistakes:

• Counting all elements without filtering
• Confusing > with >=
• Assuming Count returns sum

4. Identify the error in this LINQ extension method usage:

var list = new List<string> {"a", "bb", "ccc"};
var result = list.Where(s => s.Length > 1).ToList();
Console.WriteLine(result);

medium

A. Where method is not available on List<string>

B. Cannot call ToList() on IEnumerable

C. Console.WriteLine prints the type name, not the list contents

D. Missing using directive for System.Collections.Generic

Solution

1. Step 1: Check LINQ method usage

   Where and ToList() are valid extension methods on List<string>.

2. Step 2: Understand Console.WriteLine behavior

   Printing 'result' directly prints the type name, not the list elements.

3. Final Answer:

   Console.WriteLine prints the type name, not the list contents -> Option C

4. Quick Check:

   Printing list object shows type name [OK]

Hint: Use string.Join or loop to print list contents [OK]

Common Mistakes:

• Thinking ToList() is invalid
• Assuming Where is unavailable on List
• Forgetting to add using System.Linq

5. How can extension methods help LINQ support querying a custom collection class without modifying its source code?

hard

A. By defining static extension methods that accept the custom collection as 'this' parameter

B. By inheriting the custom collection from List<T> and overriding methods

C. By rewriting the custom collection to implement IQueryable interface

D. By adding query methods directly inside the custom collection class

Solution

1. Step 1: Understand extension methods role

   Extension methods add new methods externally without changing original class code.

2. Step 2: Apply to custom collection

   Defining static extension methods with 'this' parameter for the custom collection enables LINQ queries without modifying it.

3. Step 3: Evaluate other options

   Inheriting or rewriting requires source changes; adding methods inside class modifies it.

4. Final Answer:

   By defining static extension methods that accept the custom collection as 'this' parameter -> Option A

5. Quick Check:

   Extension methods extend without modifying class [OK]

Hint: Use static extension methods with 'this' on custom type [OK]

Common Mistakes:

• Thinking inheritance is required
• Assuming interface implementation is mandatory
• Trying to modify original class source