Reference assignment and shared state in C Sharp (C#) - Cheat Sheet & Quick Revision

Recall & Review

beginner

What happens when you assign one reference type variable to another in C#?

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

beginner

Explain shared state in the context of reference assignment.

Shared state means multiple variables refer to the same object, so modifying the object via any variable changes the state seen by all.

beginner

Consider this code:<br><pre>class Box { public int Value; }<br>Box a = new Box();<br>a.Value = 5;<br>Box b = a;<br>b.Value = 10;</pre><br>What is the value of <code>a.Value</code> after this code runs?

The value of a.Value is 10 because a and b reference the same object.

intermediate

How can you avoid shared state when working with reference types?

Create a new object (a copy) instead of assigning the reference, so each variable points to a separate object.

beginner

Why is understanding reference assignment important in programming?

Because it helps prevent bugs caused by unexpected changes to shared objects and helps manage how data is shared or isolated.

What does assigning one reference variable to another do in C#?

A Both variables point to the same object.

B Creates a new copy of the object.

C Deletes the original object.

D Copies only the values, not the reference.

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

If you change a property of an object through one reference, what happens to other references to the same object?

A They point to a new object.

B They see the updated property value.

C They become null.

D They keep the old property value.

All references to the same object see the updated property because they share the same state.

How can you create a separate object to avoid shared state?

A Declare the variable as static.

B Assign one reference to another.

C Use the 'ref' keyword.

D Use the 'new' keyword to create a new instance.

Using 'new' creates a new object instance, so variables do not share the same state.

Which of these is a value type in C# that does NOT share state on assignment?

A class

B string

C int

D array

int is a value type, so assignment copies the value, not the reference.

What is a common problem caused by shared state?

A Unexpected changes to data.

B Compilation errors.

C Slower program startup.

D Syntax errors.

Shared state can cause bugs because changes through one reference affect others unexpectedly.

Describe what happens when you assign one reference type variable to another in C# and how it relates to shared state.

Think about how variables point to objects in memory.

Explain how you can avoid shared state when working with objects in C#.

Consider how to make variables point to different objects.

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