Why reflection is needed in C Sharp (C#) - The Real Reasons

The Big Idea

What if your program could discover and use new features all by itself, without you rewriting code?

The Scenario

Imagine you have a big box of different tools, but you don't know what each tool is or what it does. You want to use the right tool, but you have to open the box and check each one manually every time.

The Problem

Manually checking each tool is slow and tiring. If you add new tools, you have to update your list every time. It's easy to make mistakes or miss something important, especially when the tools change often.

The Solution

Reflection lets your program look inside itself or other objects to find out what tools (properties, methods) they have, without needing a fixed list. It's like having a smart helper who can quickly identify and use the right tool automatically.

Before vs After

✗ Before

if (obj is Car) { var speed = ((Car)obj).Speed; } else if (obj is Bike) { var speed = ((Bike)obj).Speed; }

✓ After

var speedProp = obj.GetType().GetProperty("Speed"); var speed = speedProp?.GetValue(obj);

What It Enables

Reflection enables programs to adapt and work with unknown or changing data and types dynamically, making them more flexible and powerful.

Real Life Example

Think of a photo app that can open many image formats without knowing them all in advance. Reflection helps it discover and use the right tools to handle each format on the fly.

Key Takeaways

Manual checking of types and properties is slow and error-prone.

Reflection allows programs to inspect and use objects dynamically.

This makes software more flexible and easier to maintain.

Practice

1. Why do programmers use reflection in C#?

easy

A. To manage memory manually

B. To write faster code by avoiding loops

C. To examine and use information about types at runtime

D. To create graphical user interfaces

Solution

1. Step 1: Understand what reflection does

   Reflection allows a program to look at its own structure, like classes and methods, while it is running.

2. Step 2: Identify the purpose of reflection

   It is used to examine and interact with types dynamically, not for speed or UI creation.

3. Final Answer:

   To examine and use information about types at runtime -> Option C

4. Quick Check:

   Reflection = runtime type info [OK]

Hint: Reflection inspects types during program run [OK]

Common Mistakes:

• Confusing reflection with UI design
• Thinking reflection speeds up code
• Believing reflection manages memory

2. Which of the following is the correct way to get the type of an object obj using reflection in C#?

easy

A. Type t = obj.GetType();

B. Type t = GetType(obj);

C. Type t = typeof(obj);

D. Type t = obj.Type();

Solution

1. Step 1: Recall the method to get an object's type

   In C#, the method GetType() is called on the object instance to get its type.

2. Step 2: Check each option's syntax

   Type t = obj.GetType(); uses obj.GetType(), which is correct. Type t = GetType(obj); and D are invalid syntax. Type t = typeof(obj); uses typeof incorrectly because it expects a type name, not an object.

3. Final Answer:

   Type t = obj.GetType(); -> Option A

4. Quick Check:

   obj.GetType() gets type [OK]

Hint: Use obj.GetType() to get runtime type [OK]

Common Mistakes:

• Using typeof with an object instance
• Calling non-existent methods like obj.Type()
• Trying to pass object to GetType as argument

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

using System;
class Program {
  static void Main() {
    var type = typeof(string);
    Console.WriteLine(type.Name);
  }
}

medium

A. string

B. String

C. System.String

D. Type

Solution

1. Step 1: Understand typeof operator

   typeof(string) returns the Type object for the string class.

2. Step 2: Check what type.Name returns

   The Name property returns the class name without namespace, which is "String" with capital S.

3. Final Answer:

   String -> Option B

4. Quick Check:

   typeof(string).Name = "String" [OK]

Hint: typeof(T).Name returns class name without namespace [OK]

Common Mistakes:

• Confusing lowercase 'string' keyword with class name
• Expecting full namespace in Name property
• Thinking output is 'Type'

4. Identify the error in this reflection code snippet:

Type t = typeof(int);
var method = t.GetMethod("Parse");
int result = method.Invoke(null, new object[] { "123" });
Console.WriteLine(result);

medium

A. Invoke returns object, needs casting to int

B. GetMethod("Parse") does not exist on int

C. typeof(int) should be typeof(Int32)

D. Invoke cannot be called with null as first argument

Solution

1. Step 1: Check method retrieval

   int (System.Int32) has a static method "Parse", so GetMethod("Parse") works.

2. Step 2: Check Invoke return type and usage

   Invoke returns an object. Assigning it directly to int causes a compile error. It needs explicit cast: (int)method.Invoke(...).

3. Final Answer:

   Invoke returns object, needs casting to int -> Option A

4. Quick Check:

   Invoke returns object, cast needed [OK]

Hint: Cast Invoke result to correct type [OK]

Common Mistakes:

• Ignoring cast from object to int
• Thinking GetMethod("Parse") is invalid
• Assuming typeof(int) is wrong

5. You want to load a plugin assembly at runtime and call its method Run without knowing the class name beforehand. Which reflection approach is best?

hard

A. Call Run method without loading assembly

B. Use typeof() with class name, then call Run directly

C. Use new operator with class name string

D. Use Assembly.Load, then find type with GetTypes(), then invoke Run method

Solution

1. Step 1: Understand dynamic plugin loading

   When class name is unknown, you must load assembly dynamically and inspect types.

2. Step 2: Use reflection to find and invoke method

   Assembly.Load loads the plugin. GetTypes() lists classes. Then you find the class with Run method and invoke it.

3. Final Answer:

   Use Assembly.Load, then find type with GetTypes(), then invoke Run method -> Option D

4. Quick Check:

   Dynamic loading needs Assembly.Load + reflection [OK]

Hint: Load assembly, find type, invoke method dynamically [OK]

Common Mistakes:

• Using typeof() without knowing class name
• Trying to instantiate class by string name directly
• Calling method without loading assembly