What if you could write object setup code once and reuse it everywhere automatically?
How constructor chaining works in C Sharp (C#) - Why You Should Know This
Start learning this pattern below
Jump into concepts and practice - no test required
Imagine you have a class with many ways to create an object, and you write separate code for each way. You repeat similar setup steps in every constructor by hand.
This manual way is slow and boring. If you want to change how the object starts, you must update every constructor. It's easy to forget one and cause bugs.
Constructor chaining lets one constructor call another inside the same class. This means you write shared setup code once, and all constructors reuse it automatically.
public class Car { public string Model; public int Year; public Car() { Model = "Unknown"; Year = 0; } public Car(string model) { Model = model; Year = 0; } public Car(string model, int year) { Model = model; Year = year; } }
public class Car { public string Model; public int Year; public Car() : this("Unknown", 0) {} public Car(string model) : this(model, 0) {} public Car(string model, int year) { Model = model; Year = year; } }
Constructor chaining makes your code cleaner, easier to maintain, and less error-prone by reusing initialization logic.
Think of ordering a pizza: you can order a plain pizza, a pizza with toppings, or a pizza with toppings and extra cheese. Instead of repeating how to make the dough each time, you start from the basic dough and add extras step by step.
Constructor chaining avoids repeating code in multiple constructors.
It helps keep object setup consistent and easy to update.
It makes your class easier to read and maintain.
Practice
Solution
Step 1: Understand constructor chaining concept
Constructor chaining means one constructor calls another constructor within the same class to reuse code.Step 2: Identify what constructor chaining does
It helps avoid repeating initialization code by calling another constructor using: this(...)syntax.Final Answer:
Call one constructor from another constructor in the same class -> Option DQuick Check:
Constructor chaining = calling another constructor [OK]
- Confusing constructor chaining with method calls
- Thinking it creates multiple objects
- Mixing it up with inheritance or overriding
Solution
Step 1: Recall constructor chaining syntax
Constructor chaining uses: this(parameters)after the constructor signature to call another constructor in the same class.Step 2: Analyze options
public MyClass() : this(5) { } uses: this(5)which correctly calls another constructor with an int parameter. public MyClass() : this() { } calls itself recursively causing error. public MyClass() : base() { } calls base class constructor, not chaining. public MyClass() { this(); } tries to call constructor inside body, which is invalid.Final Answer:
public MyClass() : this(5) { } -> Option CQuick Check:
Constructor chaining syntax =: this(...)[OK]
- Using 'this()' inside constructor body instead of after signature
- Confusing base() with this()
- Calling the same constructor recursively
class Test {
public Test() : this(10) {
Console.WriteLine("Default constructor");
}
public Test(int x) {
Console.WriteLine($"Constructor with {x}");
}
}
class Program {
static void Main() {
Test t = new Test();
}
}Solution
Step 1: Understand constructor chaining call order
The parameterless constructor callsthis(10), so the constructor with int parameter runs first.Step 2: Trace output order
First, "Constructor with 10" is printed from the int constructor. Then control returns to parameterless constructor which prints "Default constructor".Final Answer:
Constructor with 10 Default constructor -> Option AQuick Check:
Chained constructor runs first, then caller prints [OK]
- Assuming calling constructor runs first
- Ignoring constructor chaining order
- Mixing output order
class Sample {
public Sample() : this() {
Console.WriteLine("Hello");
}
}Solution
Step 1: Analyze constructor chaining call
The constructor calls itself with: this(), causing infinite recursion.Step 2: Identify error type
This recursive call leads to a runtime stack overflow error because no termination occurs.Final Answer:
Recursive constructor call causing infinite loop -> Option BQuick Check:
Constructor calling itself = infinite recursion [OK]
- Thinking chaining to self is allowed
- Confusing base() and this() calls
- Expecting constructor to have return type
new Box()?class Box {
public int Width, Height;
public Box() : this(5, 10) {
Console.WriteLine("Default Box");
}
public Box(int w, int h) {
Width = w;
Height = h;
Console.WriteLine($"Box: {Width}x{Height}");
}
}Solution
Step 1: Understand constructor chaining and initialization
The parameterless constructor callsthis(5, 10), so the two-parameter constructor runs first, setting Width and Height and printing their values.Step 2: Trace output order
First, "Box: 5x10" is printed from the two-parameter constructor. Then control returns to the parameterless constructor which prints "Default Box".Final Answer:
Box: 5x10 Default Box -> Option AQuick Check:
Chained constructor runs first, then caller prints [OK]
- Assuming default values 0 for Width and Height
- Thinking default constructor runs first
- Ignoring chaining call order
