Passing reference types to methods in C Sharp (C#) - Step-by-Step Execution

Concept Flow - Passing reference types to methods

Create object in memory

↓

Pass object reference to method

↓

Method receives reference

↓

Modify object properties

↓

Return from method

↓

Original object reflects changes

When you pass a reference type to a method, the method gets a reference to the same object, so changes inside the method affect the original object.

Execution Sample

C Sharp (C#)

class Person {
  public string Name;
}

void ChangeName(Person p) {
  p.Name = "Alice";
}

Person person = new Person();
person.Name = "Bob";
ChangeName(person);

This code creates a Person object with Name 'Bob', passes it to ChangeName, which changes the Name to 'Alice'.

Execution Table

Step	Action	Variable/Parameter	Value Before	Value After	Notes
1	Create Person object	person	null	Person instance with Name=null	Object created in memory
2	Assign Name	person.Name	null	"Bob"	Set initial name to Bob
3	Call ChangeName(person)	p (parameter)	null	Reference to person object	Method receives reference
4	Inside ChangeName: p.Name = "Alice"	p.Name	"Bob"	"Alice"	Name property changed via reference
5	Return from ChangeName	person.Name	"Alice"	"Alice"	Original object reflects change

💡 Method ends; original object's Name is now 'Alice' because reference was passed

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
person.Name	null	"Bob"	"Alice"	"Alice"
p.Name	null	N/A	"Alice"	N/A (parameter scope ends)

Key Moments - 3 Insights

Why does changing p.Name inside the method affect person.Name outside?

Because p is a reference to the same object as person, so modifying p.Name changes the original object's property (see execution_table step 4).

Does the method get a copy of the object or the reference?

The method gets a copy of the reference, not the object itself. Both person and p point to the same object (see execution_table step 3).

What if we assign p = new Person() inside the method?

Assigning p to a new object changes only the local reference p, not the original person variable outside the method.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what is the value of p.Name after assignment?

A null

B "Bob"

C "Alice"

D Undefined

💡 Hint

Check the 'Value After' column for step 4 in execution_table.

At which step does the original person.Name change to "Alice"?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at when p.Name is assigned "Alice" inside the method in execution_table.

If inside ChangeName we assign p = new Person(), what happens to person.Name outside?

A person.Name remains unchanged

B person.Name changes to new object's Name

C person becomes null

D person.Name becomes null

💡 Hint

Remember that assigning p to new object changes only local reference, original person stays same.

Concept Snapshot

Passing reference types means methods get a reference to the same object.
Changes to object properties inside the method affect the original object.
The method parameter holds a copy of the reference, not a copy of the object.
Assigning the parameter to a new object does not affect the original reference.
Use this to modify objects inside methods easily.

Full Transcript

In C#, when you pass a reference type like an object to a method, the method receives a copy of the reference pointing to the same object in memory. This means if the method changes properties of the object, those changes are visible outside the method. For example, if you have a Person object with a Name property set to 'Bob' and pass it to a method that changes Name to 'Alice', after the method call, the original Person's Name will be 'Alice'. However, if inside the method you assign the parameter to a new object, this does not affect the original object outside. This behavior is because the reference itself is passed by value, but it points to the same object. Understanding this helps you predict how objects behave when passed to methods.

Practice

1. What happens when you pass a reference type object to a method in C# without using ref keyword?

easy

A. The method can modify the object's properties, affecting the original object.

B. The method cannot modify the object's properties at all.

C. The method receives a copy of the object and changes do not affect the original.

D. The method can reassign the original reference to a new object automatically.

Solution

1. Step 1: Understand passing reference types

   When a reference type is passed to a method, the method receives a copy of the reference, pointing to the same object.

2. Step 2: Effect on object properties

   Modifying the object's properties inside the method changes the original object because both references point to the same memory.

3. Final Answer:

   The method can modify the object's properties, affecting the original object. -> Option A

4. Quick Check:

   Reference type properties change original [OK]

Hint: Reference types allow property changes to affect original object [OK]

Common Mistakes:

• Thinking the object is copied entirely
• Confusing reference and value types
• Assuming reassignment changes original reference

2. Which of the following method signatures correctly allows a method to reassign a reference type parameter so the caller sees the new object?

easy

A. void UpdateObject(MyClass obj) { obj = new MyClass(); }

B. void UpdateObject(ref MyClass obj) { obj = new MyClass(); }

C. void UpdateObject(out MyClass obj) { obj = new MyClass(); }

D. void UpdateObject(in MyClass obj) { obj = new MyClass(); }

Solution

1. Step 1: Understand parameter passing keywords

   The ref keyword allows the method to reassign the caller's reference variable.

2. Step 2: Analyze each signature

   void UpdateObject(ref MyClass obj) { obj = new MyClass(); } uses ref and assigns a new object, so the caller's reference changes. void UpdateObject(MyClass obj) { obj = new MyClass(); } reassigns local copy only. void UpdateObject(out MyClass obj) { obj = new MyClass(); } requires assignment but is for output parameters. void UpdateObject(in MyClass obj) { obj = new MyClass(); } is readonly and cannot reassign.

3. Final Answer:

   void UpdateObject(ref MyClass obj) { obj = new MyClass(); } -> Option B

4. Quick Check:

   Use ref to reassign reference type parameter [OK]

Hint: Use ref keyword to let method reassign caller's reference [OK]

Common Mistakes:

• Using no keyword and expecting reassignment to affect caller
• Confusing out and ref keywords
• Trying to reassign with in parameter

3. What is the output of the following C# code?

class Person {
  public string Name;
}

void ChangeName(Person p) {
  p.Name = "Alice";
  p = new Person();
  p.Name = "Bob";
}

Person person = new Person();
person.Name = "John";
ChangeName(person);
Console.WriteLine(person.Name);

medium

A. John

B. null

C. Bob

D. Alice

Solution

1. Step 1: Trace property change before reassignment

   The method sets p.Name = "Alice", changing the original object's Name to "Alice".

2. Step 2: Reassignment inside method does not affect caller

   Then p is assigned a new Person object with Name "Bob", but this does not affect the original reference outside the method.

3. Final Answer:

   Alice -> Option D

4. Quick Check:

   Property change affects original; reassignment does not [OK]

Hint: Property changes affect original; reassignment inside method does not [OK]

Common Mistakes:

• Thinking reassignment changes original reference
• Expecting output to be 'Bob'
• Ignoring property change before reassignment

4. Identify the error in the following code that tries to update a reference type parameter so the caller sees the new object:

class Data {
  public int Value;
}

void ResetData(Data d) {
  d = new Data();
  d.Value = 0;
}

Data data = new Data();
data.Value = 5;
ResetData(data);
Console.WriteLine(data.Value);

medium

A. The method should use ref keyword to reassign the caller's reference.

B. The method should not create a new object inside.

C. The method should assign d.Value = 5 instead of 0.

D. The method should return the new object instead of void.

Solution

1. Step 1: Understand reassignment effect without ref

   Assigning d = new Data() inside the method only changes the local copy of the reference, not the caller's variable.

2. Step 2: Fix by using ref keyword

   Using ref in the method parameter and call allows the method to reassign the caller's reference to the new object.

3. Final Answer:

   The method should use ref keyword to reassign the caller's reference. -> Option A

4. Quick Check:

   Use ref to reassign reference type parameter [OK]

Hint: Use ref keyword to let method reassign caller's reference [OK]

Common Mistakes:

• Expecting reassignment without ref to affect caller
• Thinking returning new object is required
• Confusing property assignment with reference reassignment

5. You want a method to update a reference type parameter's properties and also optionally replace the whole object with a new one, so the caller sees all changes. Which approach correctly achieves this in C#?

hard

A. Pass the object with out keyword; assign new object inside method but do not modify properties.

B. Pass the object normally and modify properties; reassigning inside method updates caller automatically.

C. Pass the object with ref keyword; modify properties and reassign new object inside method.

D. Pass the object with in keyword; modify properties but cannot reassign the object.

Solution

1. Step 1: Understand property modification vs reassignment

   Modifying properties affects original object without ref, but reassignment does not affect caller unless ref is used.

2. Step 2: Use ref to allow both property changes and reassignment

   Passing with ref lets method modify properties and replace the object so caller sees all changes.

3. Final Answer:

   Pass the object with ref keyword; modify properties and reassign new object inside method. -> Option C

4. Quick Check:

   Use ref to modify and reassign reference type parameter [OK]

Hint: Use ref to modify properties and reassign object in method [OK]

Common Mistakes:

• Assuming normal pass allows reassignment to affect caller
• Using out when input object is needed
• Using in which forbids reassignment