Services
Technology Web App Development Mobile App Development Windows App Development Database Development UI/UX Development Cloud Development SEO Digital Marketing Guest Posting Content Writing Artificial Intelligence Data Science ERP Development CRM Development CMS Development LMS Development Business Listing Blockchain Technology Startup Promotion
Products
Data Converter Cleaner TUC - Unit Converter Import Export Survey Manager Tweet Controller
Developer
Article Blog Forum Interview Beginner News Startup Quiz
Users
Career
Apply Job Internship
Pricing
Login Sign Up Get a Quote

forum

home / developersection / forums / difference between abstract class and interface with example.
Ask Question

Difference between Abstract Class and Interface with example.

Anubhav Sharma 453 10 Jun 2025

Difference between Abstract Class and Interface with example.

c# c#
Updated 12 Jun 2025
Anubhav Sharma
Anubhav Sharma

Student

The Anubhav portal was launched in March 2015 at the behest of the Hon'ble Prime Minister for retiring government officials to leave a record of their experiences while in Govt service .

Message

1 Answers

Ravi Vishwakarma
Ravi Vishwakarma 12 Jun 2025
Report Abuse

Both abstract classes and interfaces define contracts for other classes to implement, but they differ in capabilities, design purpose, and usage.

Quick Comparison Table

Feature Abstract Class Interface
Inheritance One abstract class per class (single inheritance) Multiple interfaces can be implemented
Members Fields, constructors, methods, properties Only method/property signatures (no fields)
Method implementation Can have implemented & abstract methods C# 8.0+: Can have default methods
Access modifiers Yes (public, protected, etc.) All members are public by default
Constructors Yes No constructors
Use case Common base with shared code Only contract definition (pure abstraction)
Performance/Size Slightly heavier Lightweight

Example: Abstract Class

public abstract class Animal
{
    public string Name { get; set; }

    public void Eat()
    {
        Console.WriteLine("Animal is eating");
    }

    public abstract void MakeSound(); // must be implemented in derived class
}

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

Usage:

Animal dog = new Dog();
dog.Eat();        // Inherited concrete method
dog.MakeSound();  // Overridden method

Example: Interface

public interface IPlayable
{
    void Play();
}

public interface IStoppable
{
    void Stop();
}

public class MediaPlayer : IPlayable, IStoppable
{
    public void Play() => Console.WriteLine("Playing...");
    public void Stop() => Console.WriteLine("Stopped.");
}

Usage:

IPlayable player = new MediaPlayer();
player.Play();

When to Use What?

Scenario Use
Need to provide base functionality Abstract class
Need to support multiple base types Interface
Design a plug-in system or API contract Interface
Need constructors or fields Abstract class
Want to share default code Abstract class (or C# 8+ interfaces)

Tip

  • Use interface when you only need contract/behavior
  • Use abstract class when you need to share logic and structure
MindStick Training