Interface vs abstract class decision in C Sharp (C#) - Hands-On Comparison

Interface vs Abstract Class Decision in C#

📖 Scenario: Imagine you are building a simple program for a zoo management system. You need to model different animals and their behaviors. Some animals can fly, some can swim, and some can do both. You want to decide when to use an interface and when to use an abstract class to organize these behaviors.

🎯 Goal: You will create an abstract class and an interface in C# to represent animal behaviors, then implement them in specific animal classes. This will help you understand when to use interfaces and when to use abstract classes.

📋 What You'll Learn

Create an abstract class called Animal with a method MakeSound().

Create an interface called IFlyable with a method Fly().

Create a class Bird that inherits from Animal and implements IFlyable.

Create a class Fish that inherits from Animal.

Implement the methods to print simple messages describing the actions.

Create instances of Bird and Fish and call their methods.

💡 Why This Matters

🌍 Real World

In real software, you often need to organize code so that different objects share some behaviors but also have unique abilities. Abstract classes and interfaces help you do this clearly and safely.

💼 Career

Understanding when to use interfaces versus abstract classes is a key skill for software developers, especially in object-oriented programming languages like C#. It helps in designing clean, maintainable, and flexible code.

1

Create the abstract class Animal

Create an abstract class called Animal with an abstract method MakeSound() that returns void.

C Sharp (C#)

abstract class Animal
{
    // Your code here
}

Hint

Use the abstract keyword before the class and method. The method should have no body.

2

Create the interface IFlyable

Create an interface called IFlyable with a method Fly() that returns void.

C Sharp (C#)

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

interface IFlyable
{
    // Your code here
}

Hint

Interfaces do not have access modifiers on methods. Just declare the method signature.

3

Create classes Bird and Fish

Create a class called Bird that inherits from Animal and implements IFlyable. Implement the methods MakeSound() to print "Bird chirps" and Fly() to print "Bird is flying". Also create a class called Fish that inherits from Animal and implements MakeSound() to print "Fish blubs".

C Sharp (C#)

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

interface IFlyable
{
    void Fly();
}

class Bird : Animal, IFlyable
{
    // Your code here
}

class Fish : Animal
{
    // Your code here
}

Hint

Use override keyword to implement abstract methods. Implement interface methods normally.

4

Create instances and call methods

Create an instance of Bird called bird and an instance of Fish called fish. Call MakeSound() on both. Call Fly() on bird.

C Sharp (C#)

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

interface IFlyable
{
    void Fly();
}

class Bird : Animal, IFlyable
{
    public override void MakeSound()
    {
        System.Console.WriteLine("Bird chirps");
    }

    public void Fly()
    {
        System.Console.WriteLine("Bird is flying");
    }
}

class Fish : Animal
{
    public override void MakeSound()
    {
        System.Console.WriteLine("Fish blubs");
    }
}

// Your code here

Hint

Create objects using new keyword and call methods with dot notation.

Practice

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

easy

A. Use an interface when you want to provide shared code to subclasses.

B. Use an interface when unrelated classes share behavior but do not share code.

C. Use an abstract class when unrelated classes share behavior but do not share code.

D. Use an abstract class only when no methods need to be implemented.

Solution

1. Step 1: Understand interfaces

   Interfaces define method signatures without implementation, so they are ideal for unrelated classes that share behavior but not code.

2. Step 2: Understand abstract classes

   Abstract classes can provide shared code and force subclasses to implement certain methods, so they are better for related classes sharing code.

3. Final Answer:

   Use an interface when unrelated classes share behavior but do not share code. -> Option B

4. Quick Check:

   Interface = unrelated classes sharing behavior [OK]

Hint: Interfaces = behavior only, abstract classes = shared code [OK]

Common Mistakes:

• Thinking abstract classes can't have implemented methods
• Using abstract class for unrelated classes
• Confusing interfaces as code providers

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

easy

A. abstract class Vehicle { public abstract void Move(); }

B. interface Vehicle { void Move(); }

C. class abstract Vehicle { public void Move(); }

D. abstract Vehicle class { void Move(); }

Solution

1. Step 1: Recall abstract class syntax

   In C#, the keyword abstract precedes class, followed by the class name and method declarations.

2. Step 2: Check each option

   abstract class Vehicle { public abstract void Move(); } correctly uses "abstract class Vehicle" and declares an abstract method. Options A, C, and D have incorrect keyword order or use interface syntax.

3. Final Answer:

   abstract class Vehicle { public abstract void Move(); } -> Option A

4. Quick Check:

   abstract class syntax = "abstract class" [OK]

Hint: abstract class keyword order: 'abstract class' [OK]

Common Mistakes:

• Swapping 'class abstract' instead of 'abstract class'
• Using interface syntax for abstract class
• Missing 'abstract' keyword before method

3. Consider the following code snippet:

interface IAnimal { void Speak(); }
abstract class Mammal { public void Breathe() { Console.WriteLine("Breathing"); } public abstract void Speak(); }
class Dog : Mammal, IAnimal { public override void Speak() { Console.WriteLine("Woof"); } }

var dog = new Dog();
dog.Breathe();
dog.Speak();

What will be the output when this code runs?

medium

A. Breathing
Woof

B. Woof
Breathing

C. Breathing

D. Compilation error due to multiple inheritance

Solution

1. Step 1: Understand class and interface usage

   The class Dog inherits from abstract class Mammal and implements interface IAnimal. It overrides Speak() and inherits Breathe().

2. Step 2: Trace method calls

   Calling dog.Breathe() prints "Breathing". Calling dog.Speak() prints "Woof" as overridden in Dog.

3. Final Answer:

   Breathing Woof -> Option A

4. Quick Check:

   Abstract class method + override = correct output [OK]

Hint: Abstract class methods run normally; override abstract methods [OK]

Common Mistakes:

• Thinking multiple inheritance causes error in C#
• Confusing order of output lines
• Missing override keyword causing compile error

4. The following code causes a compilation error. What is the main reason?

abstract class Shape {
  public abstract void Draw();
}

class Circle : Shape {
  public void Draw() {
    Console.WriteLine("Drawing Circle");
  }
}

medium

A. Draw() method must be static in Circle.

B. Abstract classes cannot have abstract methods.

C. Circle cannot inherit from Shape because Shape is abstract.

D. Circle must declare Draw() as override, not just public.

Solution

1. Step 1: Identify abstract method implementation rules

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

2. Step 2: Check Circle class method

   The Draw() method in Circle is declared as public void Draw() but missing override, causing a compile error.

3. Final Answer:

   Circle must declare Draw() as override, not just public. -> 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 on abstract method implementation
• Thinking abstract classes can't have abstract methods
• Assuming static needed for overridden methods

5. You need to design a system where multiple unrelated classes must implement a method Log() but also share some common logging code. Which approach is best in C#?

hard

A. Use only an interface ILogger with Log() method and no shared code.

B. Use only an abstract class with Log() as abstract method and shared code implemented.

C. Create an interface ILogger with Log() and a separate abstract class with shared code, then have classes implement both.

D. Use a concrete class with Log() and inherit it in all classes.

Solution

1. Step 1: Analyze requirements

   Multiple unrelated classes must implement Log() and share some common code.

2. Step 2: Choose interface and abstract class combination

   Interfaces allow unrelated classes to share method signatures. Abstract classes can provide shared code. Classes can implement interface and inherit abstract class to get both.

3. Step 3: Evaluate other options

   Using only abstract class limits inheritance to related classes. Using only interface lacks shared code. Concrete class inheritance limits flexibility.

4. Final Answer:

   Create an interface ILogger with Log() and a separate abstract class with shared code, then have classes implement both. -> Option C

5. Quick Check:

   Interface + abstract class = behavior + shared code [OK]

Hint: Combine interface for behavior and abstract class for shared code [OK]

Common Mistakes:

• Trying to use only abstract class for unrelated classes
• Ignoring shared code needs
• Assuming multiple inheritance of classes is allowed