Why events are needed in C Sharp (C#) - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare an event in C#.

C Sharp (C#)

public event EventHandler [1];

Drag options to blanks, or click blank then click option'

AClick

BOnClick

CClicked

DClickEvent

Attempts:

3 left

💡 Hint

Common Mistakes

Using method-like names with 'On' prefix for the event declaration.

Using past tense verbs for event names.

The event name is typically a noun or noun phrase like Click. Here, Click is the correct event name.

2fill in blank

medium

Complete the code to subscribe to an event named Click.

C Sharp (C#)

button.Click [1]= Button_ClickHandler;

Drag options to blanks, or click blank then click option'

A+

B-

C+=

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '+' instead of '+='.

Using '==' which is a comparison operator.

To subscribe to an event in C#, use the += operator.

3fill in blank

hard

Fix the error in the event handler signature for the Click event.

C Sharp (C#)

private void Button_ClickHandler(object [1], EventArgs e) { /* handler code */ }

Drag options to blanks, or click blank then click option'

Aobj

Bsource

CeventSource

Dsender

Attempts:

3 left

💡 Hint

Common Mistakes

Using arbitrary parameter names that confuse the event source.

Using names that don't clearly indicate the sender.

The first parameter of an event handler is conventionally named sender, representing the source of the event.

4fill in blank

hard

Fill both blanks to raise an event safely in C#.

C Sharp (C#)

EventHandler handler = [1];
if (handler [2] null) handler(this, EventArgs.Empty);

Drag options to blanks, or click blank then click option'

AClick

B!=

C==

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Checking if handler == null instead of != null.

Using wrong variable names.

Assign the event to a local variable (here Click) and check if it is not null before invoking it.

5fill in blank

hard

Fill all three blanks to declare, subscribe, and raise an event named DataReceived.

C Sharp (C#)

public event EventHandler [1];

void Subscribe() {
    [2] += OnDataReceived;
}

void Raise() {
    [3] handler = [2];
    if (handler != null) handler(this, EventArgs.Empty);
}

Drag options to blanks, or click blank then click option'

ADataReceived

BEventHandler

Cvar

DEventArgs

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for the event in different places.

Using incorrect types for the handler variable.

The event is named DataReceived. Subscription uses the event name DataReceived. Use EventHandler as the type for the local handler variable.

Practice

1. Why are events needed in C# programming?

easy

A. To allow different parts of a program to communicate without being tightly connected

B. To make the program run faster by using multiple threads

C. To store data permanently on disk

D. To create user interfaces with buttons and text boxes

Solution

1. Step 1: Understand the purpose of events

   Events let different parts of a program talk to each other without needing to know details about each other.

2. Step 2: Compare with other options

   Options B, C, and D describe other programming tasks but not the main reason for events.

3. Final Answer:

   To allow different parts of a program to communicate without being tightly connected -> Option A

4. Quick Check:

   Events enable loose communication = A [OK]

Hint: Events connect parts without tight links [OK]

Common Mistakes:

• Confusing events with threading
• Thinking events store data
• Assuming events create UI elements

2. Which of the following is the correct way to declare an event in C#?

easy

A. public event EventHandler MyEvent;

B. public void event MyEvent();

C. event public MyEvent EventHandler;

D. public EventHandler event MyEvent;

Solution

1. Step 1: Recall C# event declaration syntax

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

2. Step 2: Check each option

   public event EventHandler MyEvent; matches the correct syntax. Options A, C, and D have incorrect order or keywords.

3. Final Answer:

   public event EventHandler MyEvent; -> Option A

4. Quick Check:

   Correct event syntax = B [OK]

Hint: Use 'public event DelegateType EventName;' [OK]

Common Mistakes:

• Placing 'event' after the delegate type
• Using 'void' with event keyword
• Mixing order of keywords

3. What will be the output of this C# code?

using System;
class Program {
  public static event Action OnChange;
  static void Main() {
    OnChange += () => Console.WriteLine("Event triggered");
    OnChange?.Invoke();
  }
}

medium

A. No output

B. Runtime error

C. Compilation error

D. Event triggered

Solution

1. Step 1: Understand event subscription and invocation

   The event OnChange is subscribed with a lambda that prints "Event triggered". Then it is invoked safely with ?.Invoke().

2. Step 2: Predict the output

   Since the event has a subscriber, invoking it prints "Event triggered" to the console.

3. Final Answer:

   Event triggered -> Option D

4. Quick Check:

   Subscribed event invoked prints message = D [OK]

Hint: Subscribed event prints message when invoked [OK]

Common Mistakes:

• Forgetting to subscribe before invoking
• Not using null-conditional operator causing errors
• Expecting no output without subscription

4. Identify the error in this C# event usage:

class MyClass {
  public event Action OnUpdate;
  public void Update() {
    OnUpdate();
  }
}

medium

A. Event OnUpdate is not subscribed before invocation

B. Event OnUpdate cannot be invoked directly without null check

C. Event OnUpdate should be declared as static

D. Event OnUpdate must return a value

Solution

1. Step 1: Check event invocation safety

   Invoking an event directly without checking if it has subscribers can cause a NullReferenceException.

2. Step 2: Identify the fix

   Use null-conditional operator or check if OnUpdate is not null before invoking.

3. Final Answer:

   Event OnUpdate cannot be invoked directly without null check -> Option B

4. Quick Check:

   Always check event is not null before invoking = A [OK]

Hint: Check event is not null before calling [OK]

Common Mistakes:

• Invoking event without null check
• Assuming events are static by default
• Expecting events to return values

5. You want to design a program where multiple parts react automatically when a data value changes. Why should you use events instead of calling methods directly?

hard

A. Events store the data changes permanently

B. Events make the program run faster by parallel processing

C. Events allow adding or removing reactions without changing the data code

D. Events prevent any part from reacting to changes

Solution

1. Step 1: Understand flexibility of events

   Events let you add or remove listeners easily without changing the code that changes data.

2. Step 2: Compare with other options

   Options A, B, and D describe unrelated or incorrect behaviors.

3. Final Answer:

   Events allow adding or removing reactions without changing the data code -> Option C

4. Quick Check:

   Events improve flexibility and decoupling = C [OK]

Hint: Events enable flexible reaction management [OK]

Common Mistakes:

• Thinking events speed up execution
• Confusing events with data storage
• Believing events block reactions