Why Custom LINQ extension methods in C Sharp (C#)? - Purpose & Use Cases

The Big Idea

What if you could teach your code new tricks that make your work feel effortless?

The Scenario

Imagine you have a list of numbers and you want to find all even numbers, then double them, and finally sum the result. Doing this by writing loops and conditions every time feels like repeating the same boring steps over and over.

The Problem

Writing loops manually is slow and easy to mess up. You might forget a condition or write extra code that makes your program hard to read and maintain. It's like copying the same recipe by hand each time instead of having a shortcut.

The Solution

Custom LINQ extension methods let you create your own reusable shortcuts that work like built-in LINQ methods. You write the logic once, then use it everywhere with simple, clear code. This makes your programs cleaner and faster to write.

Before vs After

✗ Before

var result = 0;
foreach(var n in numbers) {
  if(n % 2 == 0) {
    result += n * 2;
  }
}

✓ After

var result = numbers.WhereEven().SelectDouble().Sum();

What It Enables

It enables you to write clear, reusable, and expressive code that feels like speaking your problem directly to the computer.

Real Life Example

Suppose you work with customer orders and want to filter only large orders, then calculate discounts. Custom LINQ methods let you write this logic once and reuse it in many parts of your app without repeating code.

Key Takeaways

Manual loops are repetitive and error-prone.

Custom LINQ extensions create reusable, readable shortcuts.

They make your code cleaner and easier to maintain.

Practice

1. What is a key requirement for creating a custom LINQ extension method in C#?

easy

A. It must be a static method inside a static class with this on the first parameter.

B. It must be an instance method inside any class.

C. It must return void and take no parameters.

D. It must be declared inside the Main method.

Solution

1. Step 1: Understand extension method structure

   Extension methods must be static methods inside static classes.

2. Step 2: Identify the special parameter usage

   The first parameter must have the this keyword to specify the type it extends.

3. Final Answer:

   It must be a static method inside a static class with this on the first parameter. -> Option A

4. Quick Check:

   Extension method = static + static class + this param [OK]

Hint: Remember: static method + static class + this param [OK]

Common Mistakes:

• Making the method non-static
• Forgetting the static class container
• Omitting the 'this' keyword on the first parameter

2. Which of the following is the correct syntax to declare a custom LINQ extension method named IsEven for IEnumerable<int>?

easy

A. public static bool IsEven(this IEnumerable<int> source) { ... }

B. public bool IsEven(IEnumerable<int> source) { ... }

C. static bool IsEven(IEnumerable<int> source) { ... }

D. public static bool IsEven(IEnumerable<int> source) { ... }

Solution

1. Step 1: Check method modifiers and parameters

   The method must be public static and have this before the first parameter to be an extension method.

2. Step 2: Verify the parameter type and method signature

   public static bool IsEven(this IEnumerable<int> source) { ... } correctly uses this IEnumerable<int> source and is static and public.

3. Final Answer:

   public static bool IsEven(this IEnumerable<int> source) { ... } -> Option A

4. Quick Check:

   Extension method syntax = public static + this param [OK]

Hint: Look for 'public static' and 'this' on first parameter [OK]

Common Mistakes:

• Missing 'this' keyword on the first parameter
• Not making the method static
• Incorrect access modifier

3. Given this custom LINQ extension method, what will be the output?

public static IEnumerable<int> GetPositive(this IEnumerable<int> source) {
    foreach (var num in source) {
        if (num > 0) yield return num;
    }
}

var numbers = new List<int> { -1, 0, 3, 5, -2 };
var result = numbers.GetPositive().ToList();
Console.WriteLine(string.Join(",", result));

medium

A. -1,0,3,5,-2

B. 0,3,5

C. 3,5,-2

D. 3,5

Solution

1. Step 1: Understand the extension method logic

   The method yields only numbers greater than zero from the source list.

2. Step 2: Apply the method to the list

   From the list [-1, 0, 3, 5, -2], only 3 and 5 are greater than zero and yielded.

3. Final Answer:

   3,5 -> Option D

4. Quick Check:

   Filter positive numbers = 3,5 [OK]

Hint: Focus on the 'if (num > 0)' filter condition [OK]

Common Mistakes:

• Including zero as positive
• Returning all numbers without filtering
• Confusing yield return with return

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

public static IEnumerable<int> FilterEven(IEnumerable<int> source) {
    foreach (var num in source) {
        if (num % 2 == 0) yield return num;
    }
}

medium

A. Cannot use 'yield return' inside a foreach loop.

B. Method should return void instead of IEnumerable<int>.

C. Missing 'this' keyword on the first parameter to make it an extension method.

D. The modulo operator '%' is not valid in C#.

Solution

1. Step 1: Check extension method signature

   The method lacks the this keyword on the first parameter, so it is not an extension method.

2. Step 2: Verify other syntax elements

   Using yield return inside a foreach is valid, and '%' is a valid operator in C#.

3. Final Answer:

   Missing 'this' keyword on the first parameter to make it an extension method. -> Option C

4. Quick Check:

   Extension method requires 'this' on first parameter [OK]

Hint: Extension methods always need 'this' on first parameter [OK]

Common Mistakes:

• Forgetting 'this' keyword
• Thinking 'yield return' is invalid in loops
• Misunderstanding the modulo operator

5. You want to create a custom LINQ extension method ToDictionaryByLength that converts an IEnumerable<string> into a Dictionary<int, List<string>>, grouping strings by their length. Which implementation correctly achieves this?

hard

A. public static Dictionary ToDictionaryByLength(IEnumerable<string> source) {
return source.ToDictionary(s => s.Length, s => new List<string> { s });
}

B. public static Dictionary ToDictionaryByLength(this IEnumerable<string> source) {
return source.GroupBy(s => s.Length)
.ToDictionary(g => g.Key, g => g.ToList());
}

C. public static Dictionary ToDictionaryByLength(this IEnumerable<string> source) {
var dict = new Dictionary();
foreach (var s in source) {
dict[s.Length] = new List<string> { s };
}
return dict;
}

D. public static Dictionary ToDictionaryByLength(this IEnumerable<string> source) {
return source.ToDictionary(s => s.Length, s => s);
}

Solution

1. Step 1: Understand grouping by length

   We need to group strings by their length, so GroupBy with key s.Length is correct.

2. Step 2: Convert groups to dictionary

   Use ToDictionary with group key and list of strings as value.

3. Step 3: Check other options

   public static Dictionary ToDictionaryByLength(IEnumerable<string> source) { return source.ToDictionary(s => s.Length, s => new List<string> { s }); } does not group; it tries to create dictionary with duplicate keys causing error. public static Dictionary ToDictionaryByLength(this IEnumerable<string> source) { var dict = new Dictionary(); foreach (var s in source) { dict[s.Length] = new List<string> { s }; } return dict; } overwrites values instead of adding to list. public static Dictionary ToDictionaryByLength(this IEnumerable<string> source) { return source.ToDictionary(s => s.Length, s => s); } tries to map to string instead of list.

4. Final Answer:

   public static Dictionary<int, List<string>> ToDictionaryByLength(this IEnumerable<string> source) { return source.GroupBy(s => s.Length) .ToDictionary(g => g.Key, g => g.ToList()); } -> Option B

5. Quick Check:

   GroupBy + ToDictionary with list = correct grouping [OK]

Hint: Use GroupBy then ToDictionary with list conversion [OK]

Common Mistakes:

• Not grouping before ToDictionary
• Overwriting dictionary entries instead of adding to list
• Returning wrong value types in dictionary