Reference assignment and shared state in C Sharp (C#)

Introduction

Reference assignment lets two variables point to the same object. This means changes through one variable affect the other because they share the same data.

When you want multiple variables to work with the same object without copying it.

When you want to save memory by not duplicating large objects.

When you want changes in one place to be seen everywhere the object is used.

Syntax

C Sharp (C#)

ClassName variable1 = new ClassName();
ClassName variable2 = variable1;

Both variable1 and variable2 now point to the same object.

Changing the object via one variable changes it for the other too.

Examples

Both box1 and box2 point to the same Box object. Changing box2.Size also changes box1.Size.

C Sharp (C#)

class Box {
    public int Size;
}

Box box1 = new Box();
box1.Size = 5;
Box box2 = box1;
box2.Size = 10;

Strings are reference types but immutable, so even if s2 points to the same string, you cannot change the string content.

C Sharp (C#)

string s1 = "hello";
string s2 = s1;

Sample Program

This program shows that changing the Size property through box2 also changes it for box1 because both variables refer to the same object.

C Sharp (C#)

using System;

class Box {
    public int Size;
}

class Program {
    static void Main() {
        Box box1 = new Box();
        box1.Size = 5;

        Box box2 = box1; // box2 points to the same object as box1
        box2.Size = 10;   // change Size via box2

        Console.WriteLine($"box1.Size = {box1.Size}");
        Console.WriteLine($"box2.Size = {box2.Size}");
    }
}

Important Notes

Reference types include classes, arrays, and delegates.

Value types like int or struct copy the data, so changes do not affect the original.

Be careful: unintended shared state can cause bugs if you change an object without realizing others use it too.

Summary

Reference assignment makes two variables point to the same object.

Changes through one variable affect the other because they share the same data.

Use reference assignment to save memory and share data, but watch out for unexpected changes.

Practice

1. What happens when you assign one reference type variable to another in C#?
ClassA a = new ClassA();
ClassA b = a;

easy

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

B. A new copy of the object is created for b.

C. The variables become independent and do not affect each other.

D. The program throws a compile-time error.

Solution

1. Step 1: Understand reference assignment

   Assigning one reference variable to another makes both variables point to the same object in memory.

2. Step 2: Effect of shared reference

   Changes made through either variable affect the same object, so both see the changes.

3. Final Answer:

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

4. Quick Check:

   Reference assignment = shared object [OK]

Hint: Reference variables share the same object after assignment [OK]

Common Mistakes:

• Thinking a new object is created on assignment
• Assuming variables become independent
• Confusing value types with reference types

2. Which of the following is the correct syntax to assign one reference variable to another in C#?

easy

A. int a = b;

B. ClassA a := b;

C. ClassA a == b;

D. ClassA a = new ClassA(); a = b;

Solution

1. Step 1: Identify correct assignment operator

   In C#, the single equals sign (=) is used for assignment, not double equals (==) or :=.

2. Step 2: Check variable types and initialization

   ClassA a = new ClassA(); a = b; correctly declares a reference variable and assigns another reference variable to it.

3. Final Answer:

   ClassA a = new ClassA(); a = b; -> Option D

4. Quick Check:

   Use = for assignment in C# [OK]

Hint: Use single = for assignment, not == or := [OK]

Common Mistakes:

• Using == instead of = for assignment
• Using := which is invalid in C#
• Assigning incompatible types without casting

3. What is the output of the following code?

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

medium

A. 5

B. 0

C. 10

D. Compilation error

Solution

1. Step 1: Understand reference assignment effect

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

2. Step 2: Trace value changes

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

3. Final Answer:

   10 -> Option C

4. Quick Check:

   Shared reference means shared data [OK]

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

Common Mistakes:

• Assuming box1.Value stays 5 after box2 changes it
• Confusing reference and value types
• Expecting a compile error due to assignment

4. Identify the error in this code snippet:

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

medium

A. p2 is used before being assigned an object.

B. Cannot assign p2 to p1 because they are different types.

C. Cannot assign string to Name property.

D. No error, code runs fine.

Solution

1. Step 1: Check variable initialization

   p2 is declared but not assigned an object before accessing p2.Name.

2. Step 2: Understand runtime error

   Accessing p2.Name causes a NullReferenceException because p2 is null.

3. Final Answer:

   p2 is used before being assigned an object. -> Option A

4. Quick Check:

   Uninitialized reference causes runtime error [OK]

Hint: Always initialize reference variables before use [OK]

Common Mistakes:

• Assuming p2 has default object automatically
• Confusing compile-time and runtime errors
• Ignoring null reference exceptions

5. Given this code, what will be the output?

class Data { public int Number; }
Data d1 = new Data() { Number = 1 };
Data d2 = new Data() { Number = 2 };
d1 = d2;
d2.Number = 5;
Console.WriteLine(d1.Number);

hard

A. 2

B. 5

C. 1

D. Compilation error

Solution

1. Step 1: Analyze reference assignment

   d1 is assigned to d2, so both point to the same object with Number initially 2.

2. Step 2: Trace value change through d2

   Changing d2.Number to 5 changes the shared object, so d1.Number is also 5.

3. Final Answer:

   5 -> Option B

4. Quick Check:

   Reference assignment shares object state [OK]

Hint: After assignment, variables share the same object state [OK]

Common Mistakes:

• Thinking d1.Number remains 1 after assignment
• Confusing value and reference types
• Expecting compile errors on assignment