Why interfaces are needed in C Sharp (C#) - See It in Action

Why interfaces are needed

📖 Scenario: Imagine you are building a simple app that manages different types of devices like printers and scanners. Each device can perform an action called Start, but the way they start is different. You want a way to make sure every device has a Start action, so your app can use any device without worrying about its details.

🎯 Goal: You will create an interface called IDevice that requires a Start method. Then, you will create two classes, Printer and Scanner, that implement this interface. Finally, you will write code to start each device using the interface, showing why interfaces help organize code and make it flexible.

📋 What You'll Learn

Create an interface called IDevice with a method Start().

Create a class Printer that implements IDevice and its Start() method.

Create a class Scanner that implements IDevice and its Start() method.

Create a list of IDevice containing one Printer and one Scanner.

Use a foreach loop to call Start() on each device and print the result.

💡 Why This Matters

🌍 Real World

Interfaces are used in software to make sure different parts of a program can work together smoothly, like different devices in a system.

💼 Career

Understanding interfaces is important for writing clean, flexible code in many programming jobs, especially in object-oriented programming.

1

Create the IDevice interface

Create an interface called IDevice with a method Start() that returns a string.

C Sharp (C#)

// Your code here

Hint

An interface is like a contract. It tells classes what methods they must have.

2

Create Printer and Scanner classes implementing IDevice

Create a class called Printer that implements IDevice and its Start() method returning the string "Printer is starting". Also create a class called Scanner that implements IDevice and its Start() method returning the string "Scanner is starting".

C Sharp (C#)

public interface IDevice
{
    string Start();
}

// Your code here

Hint

Use : IDevice after the class name to say it implements the interface.

3

Create a list of IDevice with Printer and Scanner

Create a list called devices of type List<IDevice> and add one Printer and one Scanner object to it.

C Sharp (C#)

public interface IDevice
{
    string Start();
}

public class Printer : IDevice
{
    public string Start()
    {
        return "Printer is starting";
    }
}

public class Scanner : IDevice
{
    public string Start()
    {
        return "Scanner is starting";
    }
}

// Your code here

Hint

Use new List<IDevice> { ... } to create the list and add objects inside curly braces.

4

Use a foreach loop to start each device and print the result

Use a foreach loop with variable device to go through devices and print the result of calling device.Start().

C Sharp (C#)

using System.Collections.Generic;

public interface IDevice
{
    string Start();
}

public class Printer : IDevice
{
    public string Start()
    {
        return "Printer is starting";
    }
}

public class Scanner : IDevice
{
    public string Start()
    {
        return "Scanner is starting";
    }
}

List devices = new List { new Printer(), new Scanner() };

// Your code here

Hint

Use Console.WriteLine(device.Start()); inside the loop to print each message.

Practice

1. Why do we use interfaces in C# programming?

easy

A. To define a contract that classes must follow

B. To store data like variables

C. To create graphical user interfaces

D. To write comments in code

Solution

1. Step 1: Understand the purpose of interfaces

   Interfaces specify methods that a class must implement, acting like a contract.

2. Step 2: Compare other options

   Options B, C, and D describe unrelated concepts: data storage, UI design, and comments.

3. Final Answer:

   To define a contract that classes must follow -> Option A

4. Quick Check:

   Interface purpose = contract [OK]

Hint: Interfaces define required methods, not data or UI [OK]

Common Mistakes:

• Confusing interfaces with classes
• Thinking interfaces store data
• Mixing interfaces with UI design

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

easy

A. enum IExample { DoWork };

B. class IExample { void DoWork(); }

C. interface IExample { void DoWork(); }

D. struct IExample { void DoWork(); }

Solution

1. Step 1: Identify interface syntax

   In C#, interfaces are declared using the keyword interface followed by the name and method signatures.

2. Step 2: Check other options

   Options A, B, and C use enum, class, and struct keywords, which are not for interfaces.

3. Final Answer:

   interface IExample { void DoWork(); } -> Option C

4. Quick Check:

   Interface keyword = interface declaration [OK]

Hint: Look for 'interface' keyword to declare interfaces [OK]

Common Mistakes:

• Using class or struct instead of interface
• Missing method signature semicolon
• Confusing enums with interfaces

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

interface IAnimal { void Speak(); }
class Dog : IAnimal { public void Speak() { Console.WriteLine("Woof"); } }
class Cat : IAnimal { public void Speak() { Console.WriteLine("Meow"); } }
static void Main() {
  IAnimal animal = new Dog();
  animal.Speak();
  animal = new Cat();
  animal.Speak();
}

medium

A. Meow Woof

B. Woof Meow

C. Woof Woof

D. Meow Meow

Solution

1. Step 1: Understand interface usage

   The variable animal is of type IAnimal and first assigned a Dog object, so calling Speak() prints "Woof".

2. Step 2: Change object and call method again

   animal is then assigned a Cat object, so calling Speak() prints "Meow".

3. Final Answer:

   Woof Meow -> Option B

4. Quick Check:

   Interface variable calls method of assigned object [OK]

Hint: Interface variable calls method of current object type [OK]

Common Mistakes:

• Assuming interface variable fixes method output
• Mixing order of outputs
• Forgetting to implement interface methods

4. Identify the error in this code snippet:

interface IVehicle { void Drive(); }
class Car : IVehicle { }

medium

A. Car class should be abstract

B. Interface IVehicle cannot be empty

C. Drive() method should have a body in interface

D. Car class must implement Drive() method

Solution

1. Step 1: Check interface implementation rules

   A class implementing an interface must provide bodies for all interface methods.

2. Step 2: Analyze given code

   Car class implements IVehicle but does not define Drive(), causing a compile error.

3. Final Answer:

   Car class must implement Drive() method -> Option D

4. Quick Check:

   Implement all interface methods [OK]

Hint: Implement all interface methods in the class [OK]

Common Mistakes:

• Thinking interface methods have bodies
• Assuming empty class is valid implementation
• Confusing abstract class requirement

5. You want to write a method that accepts any object that can be saved to a database. Which approach best uses interfaces to achieve this?

hard

A. Define an interface ISaveable with method Save(), then accept ISaveable parameter

B. Use object type parameter and check type inside method

C. Create a base class Saveable and inherit from it

D. Write separate methods for each class type

Solution

1. Step 1: Understand interface benefits

   Interfaces allow different classes to share a common method signature, enabling polymorphism.

2. Step 2: Analyze options for flexibility and maintainability

   Define an interface ISaveable with method Save(), then accept ISaveable parameter uses an interface ISaveable with Save() method, allowing any class implementing it to be passed in.

3. Step 3: Compare other options

   Use object type parameter and check type inside method uses object and type checks, which is less clean. Create a base class Saveable and inherit from it uses inheritance, which is less flexible. Write separate methods for each class type duplicates code.

4. Final Answer:

   Define an interface ISaveable with method Save(), then accept ISaveable parameter -> Option A

5. Quick Check:

   Interfaces enable flexible method parameters [OK]

Hint: Use interface parameters for flexible method inputs [OK]

Common Mistakes:

• Using object and type checks instead of interfaces
• Relying only on inheritance
• Writing duplicate methods for each type