When to use abstract vs concrete in C Sharp (C#)

Introduction

Abstract and concrete classes help organize code by defining what things must do and what things actually do. Abstract classes set rules, while concrete classes do the real work.

When you want to define a general idea but leave details for others to fill in.

When you have common code shared by many classes but some parts differ.

When you want to prevent creating objects directly from a class that is incomplete.

When you want to create objects that do specific tasks based on a shared plan.

When you want to enforce certain methods to be implemented by all subclasses.

Syntax

C Sharp (C#)

abstract class Animal
{
    public abstract void MakeSound();
}

class Dog : Animal
{
    public override void MakeSound()
    {
        Console.WriteLine("Woof!");
    }
}

An abstract class cannot be instantiated directly.

A concrete class can be instantiated and must implement all abstract members.

Examples

Abstract class Vehicle defines a method without body. Concrete class Car provides the actual method.

C Sharp (C#)

abstract class Vehicle
{
    public abstract void StartEngine();
}

class Car : Vehicle
{
    public override void StartEngine()
    {
        Console.WriteLine("Car engine started.");
    }
}

Abstract Shape defines a method to get area. Circle implements it with its own formula.

C Sharp (C#)

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

class Circle : Shape
{
    private double radius;
    public Circle(double radius) { this.radius = radius; }
    public override double GetArea() { return Math.PI * radius * radius; }
}

Concrete class Calculator has a fully implemented method and can be used directly.

C Sharp (C#)

class Calculator
{
    public int Add(int a, int b) { return a + b; }
}

Sample Program

This program shows an abstract class Animal with an abstract method MakeSound. Concrete classes Dog and Cat implement this method. You cannot create an Animal directly, but you can create Dog and Cat objects and call their sounds.

C Sharp (C#)

using System;

abstract class Animal
{
    public abstract void MakeSound();
}

class Dog : Animal
{
    public override void MakeSound()
    {
        Console.WriteLine("Woof!");
    }
}

class Cat : Animal
{
    public override void MakeSound()
    {
        Console.WriteLine("Meow!");
    }
}

class Program
{
    static void Main()
    {
        // Animal animal = new Animal(); // Error: Cannot create instance of abstract class

        Dog dog = new Dog();
        Cat cat = new Cat();

        Console.WriteLine("Dog says:");
        dog.MakeSound();

        Console.WriteLine("Cat says:");
        cat.MakeSound();
    }
}

Important Notes

Time complexity: Using abstract classes does not affect runtime speed directly; it organizes code structure.

Space complexity: Abstract classes do not add extra memory overhead compared to concrete classes.

Common mistake: Trying to create an instance of an abstract class causes a compile error.

Use abstract classes when you want to force subclasses to implement certain methods. Use concrete classes when you want to create objects that do actual work.

Summary

Abstract classes define what must be done but not how.

Concrete classes provide the actual working code.

Use abstract classes to create a common plan and concrete classes to build specific things.

Practice

1. Which statement best describes when to use an abstract class in C#?

easy

A. When you want to define a common plan without providing full implementation.

B. When you want to create a fully working class that can be instantiated.

C. When you want to prevent inheritance altogether.

D. When you want to create a class with only static methods.

Solution

1. Step 1: Understand abstract class purpose

   An abstract class defines methods or properties that must be implemented by subclasses but does not provide full implementation itself.

2. Step 2: Compare with concrete class

   Concrete classes provide full working code and can be instantiated, unlike abstract classes.

3. Final Answer:

   When you want to define a common plan without providing full implementation. -> Option A

4. Quick Check:

   Abstract class = common plan without full code [OK]

Hint: Abstract = plan only, Concrete = full working code [OK]

Common Mistakes:

• Confusing abstract with concrete classes
• Thinking abstract classes can be instantiated
• Believing abstract classes provide full method bodies

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

easy

A. class abstract Vehicle { }

B. public abstract class Vehicle { }

C. abstract public Vehicle { }

D. public class abstract Vehicle { }

Solution

1. Step 1: Recall C# syntax for abstract classes

   The correct syntax places the keyword abstract before class and then the class name.

2. Step 2: Check each option

   public abstract class Vehicle { } uses public abstract class Vehicle { }, which is correct. Other options have incorrect keyword order or missing keywords.

3. Final Answer:

   public abstract class Vehicle { } -> Option B

4. Quick Check:

   abstract class syntax = 'public abstract class' [OK]

Hint: Use 'abstract' before 'class' keyword [OK]

Common Mistakes:

• Placing 'abstract' after 'class'
• Omitting 'class' keyword
• Incorrect keyword order

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

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

class Dog : Animal {
    public override void Speak() {
        Console.WriteLine("Woof");
    }
}

class Program {
    static void Main() {
        Animal a = new Dog();
        a.Speak();
    }
}

medium

A. Runtime error because Speak is abstract

B. Compile-time error because Animal is abstract

C. Woof

D. No output

Solution

1. Step 1: Understand abstract method implementation

   The abstract method Speak in Animal is overridden in Dog with a concrete implementation that prints "Woof".

2. Step 2: Analyze runtime behavior

   Creating an Animal reference to a Dog object and calling Speak() calls the overridden method, printing "Woof".

3. Final Answer:

   Woof -> Option C

4. Quick Check:

   Abstract method overridden = prints 'Woof' [OK]

Hint: Abstract method must be overridden to run [OK]

Common Mistakes:

• Thinking abstract class cannot be referenced
• Expecting compile or runtime error
• Assuming abstract methods have bodies

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 must declare Area() as override

B. Shape cannot have abstract methods

C. Circle cannot inherit from Shape

D. Area method should return int, not double

Solution

1. Step 1: Check abstract method override rules

   When a class inherits an abstract method, it must override it using the override keyword.

2. Step 2: Identify missing override keyword

   The Circle class defines Area() but misses override, causing a compile error.

3. Final Answer:

   Circle must declare Area() as override -> Option A

4. Quick Check:

   Override keyword required for abstract methods [OK]

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

Common Mistakes:

• Omitting override keyword
• Thinking abstract methods can be ignored
• Confusing return types

5. You want to design a system where all vehicles must have a method StartEngine(), but the way engines start differs by vehicle type. Which approach is best in C#?

hard

A. Create a static class Vehicle with static StartEngine() method.

B. Create a concrete class Vehicle with a fully implemented StartEngine() method for all vehicles.

C. Use an interface with a concrete StartEngine() method and inherit it in all vehicle classes.

D. Create an abstract class Vehicle with abstract method StartEngine(), then implement it in subclasses.

Solution

1. Step 1: Analyze requirement for different implementations

   Since StartEngine() differs by vehicle type, it should be declared abstract to force subclasses to provide their own version.

2. Step 2: Choose correct class design

   An abstract class Vehicle with an abstract StartEngine() method fits best, allowing subclasses to implement specific behavior.

3. Final Answer:

   Create an abstract class Vehicle with abstract method StartEngine(), then implement it in subclasses. -> Option D

4. Quick Check:

   Abstract class for common plan, concrete for specifics [OK]

Hint: Abstract method for varying behavior, concrete class for details [OK]

Common Mistakes:

• Using concrete class with one method for all vehicles
• Trying to put method body in interface (not allowed)
• Using static class which can't be inherited