Why EventHandler delegate pattern in C Sharp (C#)? - Purpose & Use Cases

The Big Idea

What if your app could listen and react to actions automatically, without messy code everywhere?

The Scenario

Imagine you have a button in your app, and you want to run some code when the button is clicked. Without a clear system, you might write separate code everywhere to check if the button was clicked, making your program messy and hard to follow.

The Problem

Manually checking for events means writing repetitive code all over your app. It's easy to forget to check or handle some cases, causing bugs. Also, changing what happens on a click means hunting through many places, which is slow and error-prone.

The Solution

The EventHandler delegate pattern lets you neatly connect actions to events like button clicks. You write the event once, then attach any number of methods to run when it happens. This keeps your code clean, organized, and easy to update.

Before vs After

✗ Before

if (buttonClicked) {
    DoSomething();
}
// Repeat checks everywhere

✓ After

button.Click += OnButtonClick;

void OnButtonClick(object sender, EventArgs e) {
    DoSomething();
}

What It Enables

This pattern makes your program respond to events smoothly, letting you add or change reactions without messy code rewrites.

Real Life Example

Think of a music player app: when you press play, pause, or stop, the EventHandler pattern lets the app react instantly and correctly, no matter how many parts need to know about the button press.

Key Takeaways

Manual event checks are repetitive and error-prone.

EventHandler delegate pattern organizes event responses cleanly.

It allows easy adding or changing of event reactions.

Practice

1. What is the main purpose of the EventHandler delegate in C#?

easy

A. To format strings for output

B. To create a new thread for event processing

C. To store data in a dictionary

D. To define a method signature for handling events

Solution

1. Step 1: Understand what a delegate does

   A delegate defines a method signature that can be used to call methods indirectly.

2. Step 2: Connect delegate to event handling

   The EventHandler delegate specifically defines the signature for methods that handle events.

3. Final Answer:

   To define a method signature for handling events -> Option D

4. Quick Check:

   EventHandler defines event method signature = D [OK]

Hint: EventHandler defines how event methods look [OK]

Common Mistakes:

• Confusing EventHandler with threading
• Thinking EventHandler stores data
• Mixing EventHandler with string formatting

2. Which of the following is the correct syntax to declare an event using the EventHandler delegate in a class?

easy

A. public event EventHandler MyEvent;

B. public EventHandler event MyEvent;

C. event public EventHandler MyEvent();

D. public void event EventHandler MyEvent;

Solution

1. Step 1: Recall event declaration syntax

   Events are declared with the keyword event followed by the delegate type and event name.

2. Step 2: Match correct syntax

   public event EventHandler MyEvent; matches the correct pattern.

3. Final Answer:

   public event EventHandler MyEvent; -> Option A

4. Quick Check:

   Event declaration = event + delegate + name [OK]

Hint: Remember: event keyword before delegate type [OK]

Common Mistakes:

• Placing 'event' after delegate type
• Adding parentheses after event name
• Using void instead of event keyword

3. What will be the output of the following code?

using System;
class Program {
    public static event EventHandler OnAction;
    static void Main() {
        OnAction += (sender, e) => Console.WriteLine("Action happened!");
        OnAction?.Invoke(null, EventArgs.Empty);
    }
}

medium

A. Action happened!

B. No output

C. NullReferenceException

D. Compilation error

Solution

1. Step 1: Understand event subscription

   The lambda expression subscribes a method that prints "Action happened!" to the event OnAction.

2. Step 2: Invoke the event safely

   The event is invoked with ?.Invoke, so it calls the subscribed method, printing the message.

3. Final Answer:

   Action happened! -> Option A

4. Quick Check:

   Subscribed event invoked prints message = A [OK]

Hint: ?.Invoke calls event only if not null [OK]

Common Mistakes:

• Forgetting to subscribe to the event
• Not using null-conditional operator causing errors
• Expecting no output without invocation

4. Identify the error in this event usage code:

public class Button {
    public event EventHandler Click;
    public void SimulateClick() {
        Click(null, EventArgs.Empty);
    }
}

medium

A. EventHandler delegate cannot use EventArgs.Empty

B. Event must be invoked with a sender object, not null

C. Event should be checked for null before invoking

D. SimulateClick method must be static

Solution

1. Step 1: Check event invocation safety

   Events can be null if no subscribers exist, so invoking without null check causes runtime error.

2. Step 2: Correct usage

   Use Click?.Invoke(this, EventArgs.Empty); to safely invoke the event.

3. Final Answer:

   Event should be checked for null before invoking -> Option C

4. Quick Check:

   Always check event for null before invoke [OK]

Hint: Use ?.Invoke to avoid null errors [OK]

Common Mistakes:

• Invoking event directly without null check
• Assuming sender cannot be null
• Making event handler static unnecessarily

5. You want to create a custom event that sends a string message to subscribers. Which is the best way to define the event and its arguments using the EventHandler pattern?

hard

A. Declare event as EventHandler and send string directly as sender parameter

B. Create a class inheriting from EventArgs with a string property, then declare event as EventHandler<YourArgs>

C. Use Action<string> delegate instead of EventHandler for the event

D. Declare event as EventHandler and ignore sending any data

Solution

1. Step 1: Understand custom event data

   To send extra info, create a class derived from EventArgs with needed properties.

2. Step 2: Use generic EventHandler with custom args

   Declare event as EventHandler<YourArgs> to pass the custom data safely.

3. Final Answer:

   Create a class inheriting from EventArgs with a string property, then declare event as EventHandler<YourArgs> -> Option B

4. Quick Check:

   Custom EventArgs + EventHandler<T> = B [OK]

Hint: Use EventHandler<T> with custom EventArgs for extra data [OK]

Common Mistakes:

• Passing data via sender parameter
• Using Action delegate instead of EventHandler
• Ignoring event data when needed