Common bugs from reference sharing in C Sharp (C#) - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is reference sharing in C#?

Reference sharing happens when two or more variables point to the same object in memory, so changes through one variable affect the others.

beginner

Why can reference sharing cause bugs?

Because modifying an object through one reference changes it for all references, leading to unexpected side effects if not intended.

intermediate

What is a common bug caused by modifying a shared list in C#?

If multiple variables share the same list reference, adding or removing items from one variable changes the list for all, which can cause logic errors.

intermediate

How can you avoid bugs from reference sharing when working with objects?

Create a copy of the object instead of sharing the reference. For example, use cloning or copy constructors to get a new independent object.

advanced

What is a shallow copy vs a deep copy in C#?

A shallow copy duplicates the top-level object but keeps references to nested objects. A deep copy duplicates everything, creating fully independent objects.

What happens if you modify an object through one reference when multiple references share it?

A The object is duplicated automatically

B Only the modified reference changes

C All references see the change

D The program crashes

Because all references point to the same object, changes through one reference affect all.

Which of these can help avoid bugs from reference sharing?

A Creating copies of objects

B Using global variables

C Sharing references everywhere

D Ignoring object state

Creating copies ensures each variable works with its own object, preventing unintended side effects.

What is a shallow copy in C#?

A Copying only primitive types

B Copying everything including nested objects

C Copying references without any duplication

D Copying only the top-level object, sharing nested objects

A shallow copy duplicates the main object but nested objects remain shared.

If two variables share a list reference, what happens when you add an item via one variable?

A The program throws an error

B The item appears in both variables' lists

C The list is duplicated automatically

D Only the first variable's list changes

Both variables point to the same list, so changes are visible through both.

Which method is NOT a way to create a copy of an object in C#?

A Assigning one variable to another

B Using a copy constructor

C Using MemberwiseClone()

D Implementing ICloneable interface

Assigning one variable to another copies the reference, not the object itself.

Explain what reference sharing is and why it can cause bugs in C# programs.

Think about how variables can point to the same object.

Describe how to avoid bugs caused by reference sharing when working with objects in C#.

Consider how to make independent objects.

Practice

1. What happens when you assign one object variable to another in C#?

easy

A. Both variables refer to the same object in memory.

B. A new independent copy of the object is created automatically.

C. The original object is deleted and replaced by the new variable.

D. The variables become unrelated and hold different objects.

Solution

1. Step 1: Understand object assignment in C#

   Assigning one object variable to another copies the reference, not the object itself.

2. Step 2: Effect of reference copying

   Both variables point to the same object in memory, so changes via one affect the other.

3. Final Answer:

   Both variables refer to the same object in memory. -> Option A

4. Quick Check:

   Reference copy = same object [OK]

Hint: Assigning objects copies references, not objects [OK]

Common Mistakes:

• Thinking a new object is created automatically
• Assuming variables hold independent objects
• Confusing value types with reference types

2. Which of the following is the correct way to create a copy of an object to avoid reference sharing in C#?

easy

A. Use a method like MemberwiseClone() or implement ICloneable.

B. Use the assignment operator (=) between two object variables.

C. Declare the object variable as readonly.

D. Use the 'new' keyword without copying fields.

Solution

1. Step 1: Identify how to copy objects in C#

   Assignment copies references, so to create a copy, you need cloning methods like MemberwiseClone() or ICloneable.

2. Step 2: Why other options are incorrect

   Assignment operator copies reference; readonly only prevents reassignment; 'new' without copying fields creates a new empty object.

3. Final Answer:

   Use a method like MemberwiseClone() or implement ICloneable. -> Option A

4. Quick Check:

   Clone method = copy object [OK]

Hint: Clone objects to avoid shared references [OK]

Common Mistakes:

• Using assignment operator expecting a copy
• Confusing readonly with copying
• Creating new object without copying data

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

class Box { public int Value; }
var box1 = new Box { Value = 5 };
var box2 = box1;
box2.Value = 10;
Console.WriteLine(box1.Value);

medium

A. 5

B. Compilation error

C. 0

D. 10

Solution

1. Step 1: Understand reference assignment in the code

   box2 is assigned box1, so both refer to the same Box object.

2. Step 2: Effect of changing box2.Value

   Changing box2.Value to 10 changes the single shared object, so box1.Value also becomes 10.

3. Final Answer:

   10 -> Option D

4. Quick Check:

   Shared reference means value changes reflect [OK]

Hint: Changing one reference changes all pointing to same object [OK]

Common Mistakes:

• Expecting box1.Value to remain 5
• Confusing value and reference types
• Assuming box2 is a separate object

4. Identify the bug in this C# code snippet related to reference sharing:

class Person { public string Name; }
var p1 = new Person { Name = "Alice" };
var p2 = p1;
p2.Name = "Bob";
Console.WriteLine(p1.Name);

medium

A. p1 and p2 refer to different objects, so no bug.

B. p2.Name change affects p1.Name because both reference the same object.

C. The code causes a null reference exception.

D. The assignment operator creates a deep copy automatically.

Solution

1. Step 1: Analyze object references in the code

   p2 is assigned p1, so both variables point to the same Person object.

2. Step 2: Effect of modifying p2.Name

   Changing p2.Name to "Bob" changes the shared object, so p1.Name also becomes "Bob".

3. Final Answer:

   p2.Name change affects p1.Name because both reference the same object. -> Option B

4. Quick Check:

   Shared reference causes shared changes [OK]

Hint: Check if variables share the same object reference [OK]

Common Mistakes:

• Assuming p1.Name remains "Alice"
• Expecting automatic deep copy on assignment
• Thinking null reference exception occurs

5. You want to create two independent lists of integers in C# so that modifying one list does not affect the other. Which code snippet correctly avoids reference sharing?

hard

A. var list1 = new List<int> {1, 2, 3}; var list2 = list1; list2.Add(4);

B. var list1 = new List<int> {1, 2, 3}; var list2 = list1; list1.Clear();

C. var list1 = new List<int> {1, 2, 3}; var list2 = new List<int>(list1); list2.Add(4);

D. var list1 = new List<int> {1, 2, 3}; var list2 = list1; list1 = new List<int>();

Solution

1. Step 1: Understand reference sharing with lists

   Assigning list2 = list1 copies the reference, so both variables point to the same list.

2. Step 2: Creating an independent copy

   Using new List<int>(list1) creates a new list copying elements, so list2 is independent.

3. Final Answer:

   var list2 = new List<int>(list1); list2.Add(4); -> Option C

4. Quick Check:

   New list constructor copies elements [OK]

Hint: Use new List<T>(existingList) to copy lists [OK]

Common Mistakes:

• Assigning list2 = list1 expecting copy
• Clearing list1 expecting list2 unaffected
• Reassigning list1 does not affect list2 reference