Why Abstract classes and methods in C Sharp (C#)? - Purpose & Use Cases

The Big Idea

What if you could guarantee every part of your program follows the same rules without writing repetitive code?

The Scenario

Imagine you are building a program for different types of vehicles. You want each vehicle to have a way to start, but each vehicle starts differently. Without a clear plan, you write separate start methods for each vehicle, repeating similar code and forgetting to include start behavior for some vehicles.

The Problem

Manually writing start methods for every vehicle type leads to repeated code and mistakes. You might forget to add a start method for a new vehicle, or write inconsistent method names. This makes your program hard to maintain and extend.

The Solution

Abstract classes and methods let you create a blueprint for vehicles. You define an abstract start method that every vehicle must implement. This ensures all vehicles have a start method, but each can have its own unique way to start. It keeps your code organized and consistent.

Before vs After

✗ Before

class Car { void Start() { /* start car */ } } class Bike { void StartBike() { /* start bike */ } }

✓ After

abstract class Vehicle { public abstract void Start(); } class Car : Vehicle { public override void Start() { /* start car */ } } class Bike : Vehicle { public override void Start() { /* start bike */ } }

What It Enables

It enables you to design clear, reusable blueprints that guarantee essential behaviors while allowing flexible implementations.

Real Life Example

Think of a remote control system where every device must have a power-on function. Using an abstract class ensures every device class implements its own power-on method, so the remote can turn on any device without knowing the details.

Key Takeaways

Abstract classes provide a blueprint for related classes.

Abstract methods force subclasses to implement specific behaviors.

This approach avoids code duplication and enforces consistency.

Practice

1. What is true about an abstract class in C#?

easy

A. It can be instantiated like any other class.

B. It must have only abstract methods.

C. It cannot be instantiated directly.

D. It cannot have any methods.

Solution

1. Step 1: Understand abstract class instantiation rules

   An abstract class is designed as a base template and cannot be created as an object directly.

2. Step 2: Check other options for correctness

   Abstract classes can have both abstract and non-abstract methods, so options A, B, and D are incorrect.

3. Final Answer:

   It cannot be instantiated directly. -> Option C

4. Quick Check:

   Abstract class = no direct instantiation [OK]

Hint: Remember: abstract classes are blueprints, not objects. [OK]

Common Mistakes:

• Thinking abstract classes can be instantiated.
• Believing abstract classes must have only abstract methods.
• Confusing abstract classes with interfaces.

2. Which of the following is the correct way to declare an abstract method in C#?

easy

A. public abstract void Display() {}

B. public abstract void Display();

C. abstract public void Display() {}

D. public void abstract Display() {}

Solution

1. Step 1: Recall abstract method syntax

   Abstract methods have no body and end with a semicolon, declared with the 'abstract' keyword before the return type.

2. Step 2: Validate each option

   public abstract void Display(); matches the correct syntax. public void abstract Display() {} and C have wrong keyword order or include a body. public abstract void Display() {} incorrectly includes a method body.

3. Final Answer:

   public abstract void Display(); -> Option B

4. Quick Check:

   Abstract method = declaration only, no body [OK]

Hint: Abstract methods end with semicolon, no braces. [OK]

Common Mistakes:

• Adding method body to abstract methods.
• Wrong keyword order in declaration.
• Using braces {} with abstract methods.

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

abstract class Animal {
    public abstract string Speak();
}

class Dog : Animal {
    public override string Speak() {
        return "Woof";
    }
}

class Program {
    static void Main() {
        Animal myDog = new Dog();
        System.Console.WriteLine(myDog.Speak());
    }
}

medium

A. Woof

B. Animal

C. Compile-time error

D. Runtime error

Solution

1. Step 1: Understand class inheritance and method override

   Dog inherits from abstract Animal and implements the abstract Speak method returning "Woof".

2. Step 2: Trace program execution

   Main creates a Dog object as Animal type and calls Speak(), which runs Dog's override returning "Woof".

3. Final Answer:

   Woof -> Option A

4. Quick Check:

   Override abstract method = Dog's Speak() output [OK]

Hint: Abstract method calls run subclass override. [OK]

Common Mistakes:

• Expecting abstract class method output.
• Thinking abstract classes can be instantiated.
• Confusing compile-time and runtime errors.

4. Identify the error in this code snippet:

abstract class Shape {
    public abstract double Area();
}

class Circle : Shape {
    public double Area() {
        return 3.14 * 5 * 5;
    }
}

medium

A. Circle class cannot inherit from Shape.

B. Area() method cannot return double.

C. Shape class cannot have abstract methods.

D. Circle must declare Area() as override.

Solution

1. Step 1: Check method overriding rules

   When a subclass implements an abstract method, it must use the 'override' keyword.

2. Step 2: Identify missing override keyword

   Circle's Area() method lacks 'override', causing a compile error.

3. Final Answer:

   Circle must declare Area() as override. -> Option D

4. Quick Check:

   Override abstract method = must use 'override' keyword [OK]

Hint: Override abstract methods with 'override' keyword. [OK]

Common Mistakes:

• Omitting 'override' keyword in subclass method.
• Thinking abstract methods can be implemented without override.
• Confusing return types.

5. You want to create a base class Vehicle with an abstract method StartEngine(). You also want to ensure every subclass implements StartEngine() differently. Which is the best approach?

hard

A. Make Vehicle an abstract class with an abstract StartEngine() method.

B. Make Vehicle a normal class and provide a default StartEngine() implementation.

C. Make Vehicle an interface with StartEngine() method.

D. Make Vehicle a sealed class with StartEngine() method.

Solution

1. Step 1: Understand requirement for different implementations

   Each subclass must implement StartEngine() differently, so a base method without body is needed.

2. Step 2: Choose correct class type and method declaration

   Abstract class Vehicle with abstract StartEngine() enforces subclasses to implement it uniquely.

3. Final Answer:

   Make Vehicle an abstract class with an abstract StartEngine() method. -> Option A

4. Quick Check:

   Abstract class + abstract method = enforced subclass implementation [OK]

Hint: Use abstract class + abstract method for enforced overrides. [OK]

Common Mistakes:

• Using sealed class which prevents inheritance.
• Using interface when base class behavior is needed.
• Providing default method when unique implementations required.