Why First, Single, and their OrDefault variants in C Sharp (C#)? - Purpose & Use Cases

The Big Idea

What if you could find exactly the item you want in a list with just one simple command, no matter how big the list is?

The Scenario

Imagine you have a long list of names and you want to find the very first name that starts with the letter 'A'. You start scanning the list one by one, checking each name carefully.

The Problem

Doing this by hand or writing long loops is slow and tiring. You might forget to stop after finding the first match, or your code might crash if no name starts with 'A'. It's easy to make mistakes and waste time.

The Solution

Using First, Single, and their OrDefault variants lets you quickly and safely get the item you want from a list. They handle the searching and errors for you, so your code stays clean and easy to read.

Before vs After

✗ Before

foreach(var name in names) {
  if(name.StartsWith("A")) {
    return name;
  }
}
throw new Exception("No match found");

✓ After

var result = names.FirstOrDefault(name => name.StartsWith("A"));

What It Enables

You can easily and safely pick exactly one item from a collection without writing complex loops or error checks.

Real Life Example

Finding the first available seat in a theater booking system or ensuring there is exactly one user with a specific email address in a database.

Key Takeaways

First gets the first matching item; Single expects exactly one match.

OrDefault versions return a safe default if no match is found, avoiding errors.

These methods simplify searching and make your code safer and cleaner.

Practice

1.

Which method will throw an exception if the collection does not have exactly one matching element?

First(), FirstOrDefault(), Single(), SingleOrDefault()

easy

A. SingleOrDefault()

B. First()

C. FirstOrDefault()

D. Single()

Solution

1. Step 1: Understand Single() behavior

   Single() expects exactly one matching element and throws if there are zero or more than one.

2. Step 2: Compare with other methods

   First() and FirstOrDefault() do not throw if multiple elements exist; SingleOrDefault() throws only if multiple elements exist but returns default if none.

3. Final Answer:

   Single() -> Option D

4. Quick Check:

   Throws on multiple matches = Single() [OK]

Hint: Single() throws if more than one match exists [OK]

Common Mistakes:

• Confusing Single() with First() which returns first match
• Thinking FirstOrDefault() throws on multiple matches
• Assuming SingleOrDefault() never throws

2.

Which of the following is the correct syntax to get the first element or default from a list numbers?

var result = numbers._____();

easy

A. Single

B. FirstOrDefault

C. First

D. SingleOrDefault

Solution

1. Step 1: Identify method for first or default

   FirstOrDefault() returns the first element or default if none found.

2. Step 2: Check syntax correctness

   numbers.FirstOrDefault() is valid syntax to get first or default.

3. Final Answer:

   FirstOrDefault -> Option B

4. Quick Check:

   FirstOrDefault() syntax correct for first or default [OK]

Hint: Use FirstOrDefault() to safely get first or default [OK]

Common Mistakes:

• Using Single() which throws if multiple elements
• Using First() which throws if empty
• Using SingleOrDefault() which expects single element

3.

What will be the output of this code?

var list = new List<int> { 5, 10, 15 };
var result = list.SingleOrDefault(x => x == 10);
Console.WriteLine(result);

medium

A. 10

B. 0

C. Throws exception

D. null

Solution

1. Step 1: Understand SingleOrDefault with predicate

   SingleOrDefault returns the only element matching predicate or default if none, throws if multiple.

2. Step 2: Check list and predicate

   List has one element equal to 10, so SingleOrDefault returns 10.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   SingleOrDefault returns single matching element = 10 [OK]

Hint: SingleOrDefault returns single match or default, throws if many [OK]

Common Mistakes:

• Expecting 0 as default when element exists
• Thinking it throws because of multiple elements in list
• Confusing with FirstOrDefault behavior

4.

Identify the error in this code snippet:

var items = new List<string> { "apple", "banana", "apple" };
var singleItem = items.Single(x => x == "apple");
Console.WriteLine(singleItem);

medium

A. Returns "apple" without error

B. Returns null because of duplicates

C. Throws InvalidOperationException due to multiple matches

D. Syntax error in lambda expression

Solution

1. Step 1: Analyze Single() with multiple matches

   Single() throws InvalidOperationException if more than one element matches the predicate.

2. Step 2: Check list contents

   List has two "apple" strings, so Single() throws exception.

3. Final Answer:

   Throws InvalidOperationException due to multiple matches -> Option C

4. Quick Check:

   Single() throws on multiple matches [OK]

Hint: Single() throws if more than one match found [OK]

Common Mistakes:

• Expecting Single() to return first match
• Thinking it returns null on duplicates
• Assuming syntax error in lambda

5.

You have a list of users and want to get the only user with the username "admin" or null if none exists. Which method should you use to avoid exceptions if there are no or multiple admins?

hard

A. FirstOrDefault()

B. SingleOrDefault() with try-catch

C. Single()

D. First()

Solution

1. Step 1: Understand requirements

   We want the only user named "admin" or null if none, but avoid exceptions if multiple exist.

2. Step 2: Evaluate methods

   SingleOrDefault() throws if multiple matches, so risky. FirstOrDefault() returns first or null safely even if multiple exist.

3. Final Answer:

   FirstOrDefault() -> Option A

4. Quick Check:

   FirstOrDefault() safely returns first or null without exceptions [OK]

Hint: Use FirstOrDefault() to avoid exceptions on multiple matches [OK]

Common Mistakes:

• Using SingleOrDefault() which throws on multiple matches
• Using Single() which throws on zero or multiple matches
• Using First() which throws if none found