Explicit interface implementation in C Sharp (C#)

Introduction

Explicit interface implementation helps when a class needs to use two interfaces that have methods with the same name. It lets you tell the computer exactly which method belongs to which interface.

When two interfaces have methods with the same name and you want to keep them separate.

When you want to hide an interface method from the class's public methods.

When you want to control how interface methods are accessed through the interface only.

When implementing multiple interfaces that might conflict in method names.

Syntax

C Sharp (C#)

class ClassName : InterfaceName {
    ReturnType InterfaceName.MethodName(Parameters) {
        // method body
    }
}

The method is written with the interface name before the method name.

These methods can only be called through an interface reference, not directly from the class object.

Examples

This class implements two interfaces with the same method name Show. Each method is implemented explicitly to keep them separate.

C Sharp (C#)

interface IFirst {
    void Show();
}

interface ISecond {
    void Show();
}

class MyClass : IFirst, ISecond {
    void IFirst.Show() {
        Console.WriteLine("First Show");
    }
    void ISecond.Show() {
        Console.WriteLine("Second Show");
    }
}

The Display method is implemented explicitly, so it can only be called through an IExample reference.

C Sharp (C#)

interface IExample {
    void Display();
}

class ExampleClass : IExample {
    void IExample.Display() {
        Console.WriteLine("Display from IExample");
    }
}

Sample Program

This program shows a class Speaker implementing two interfaces with the same method Speak explicitly. We call each method through the interface references to get different outputs.

C Sharp (C#)

using System;

interface IAlpha {
    void Speak();
}

interface IBeta {
    void Speak();
}

class Speaker : IAlpha, IBeta {
    void IAlpha.Speak() {
        Console.WriteLine("Alpha speaks");
    }

    void IBeta.Speak() {
        Console.WriteLine("Beta speaks");
    }
}

class Program {
    static void Main() {
        Speaker sp = new Speaker();

        IAlpha alpha = sp;
        IBeta beta = sp;

        alpha.Speak();
        beta.Speak();

        // sp.Speak(); // This would cause a compile error
    }
}

Important Notes

You cannot call explicitly implemented methods directly from the class object.

Explicit implementation helps avoid name conflicts in multiple interface inheritance.

Use explicit implementation when you want to hide interface methods from the class's public API.

Summary

Explicit interface implementation separates methods with the same name from different interfaces.

These methods are only accessible through the interface, not the class object.

This technique helps avoid confusion and name conflicts in complex designs.

Practice

1. What is the main purpose of explicit interface implementation in C#?

easy

A. To separate methods with the same name from different interfaces

B. To make interface methods public by default

C. To allow interface methods to be called without casting

D. To override base class methods automatically

Solution

1. Step 1: Understand interface method conflicts

   When a class implements multiple interfaces with methods of the same name, explicit implementation helps separate them.

2. Step 2: Recognize explicit implementation behavior

   Explicit interface methods are only accessible through the interface, avoiding confusion and conflicts.

3. Final Answer:

   To separate methods with the same name from different interfaces -> Option A

4. Quick Check:

   Explicit interface implementation = separate same-named methods [OK]

Hint: Explicit means access only via interface, not class object [OK]

Common Mistakes:

• Thinking explicit makes methods public on the class
• Assuming explicit allows calling without casting
• Confusing explicit with overriding base methods

2. Which of the following is the correct syntax for explicit interface implementation of method Show() from interface IExample in class Demo?

easy

A. public void Show() { }

B. public void IExample.Show() { }

C. void IExample.Show() { }

D. void Show() IExample { }

Solution

1. Step 1: Recall explicit implementation syntax

   Explicit interface methods are implemented with the interface name before the method: void InterfaceName.MethodName().

2. Step 2: Match correct syntax

   void IExample.Show() { } matches this pattern exactly: void IExample.Show() { }.

3. Final Answer:

   void IExample.Show() { } -> Option C

4. Quick Check:

   Explicit syntax = void Interface.Method() [OK]

Hint: Explicit methods use interface name before method [OK]

Common Mistakes:

• Adding public modifier to explicit method
• Placing interface name after method name
• Using invalid syntax like 'void Show() IExample'

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

interface IA { void Display(); }
interface IB { void Display(); }
class Test : IA, IB {
    void IA.Display() { Console.WriteLine("IA Display"); }
    void IB.Display() { Console.WriteLine("IB Display"); }
}

var obj = new Test();
// obj.Display(); // Line A
((IA)obj).Display();
((IB)obj).Display();

medium

A. Compilation error at Line A

B. IA Display\nIB Display

C. IB Display\nIA Display

D. Runtime error

Solution

1. Step 1: Understand explicit interface calls

   Explicit interface methods cannot be called directly on the class object, so obj.Display() causes error if uncommented.

2. Step 2: Check interface casts and calls

   Casting to IA calls IA.Display() printing "IA Display"; casting to IB calls IB.Display() printing "IB Display".

3. Final Answer:

   IA Display IB Display -> Option B

4. Quick Check:

   Explicit calls via interface = correct output [OK]

Hint: Call explicit methods only via interface cast [OK]

Common Mistakes:

• Trying to call explicit method directly on class object
• Mixing output order
• Expecting runtime errors instead of compile errors

4. Identify the error in the following code snippet implementing explicit interface method:

interface IAlpha { void Run(); }
class Beta : IAlpha {
    public void IAlpha.Run() {
        Console.WriteLine("Running");
    }
}

medium

A. Explicit interface method cannot have public modifier

B. Method name must be different from interface

C. Interface name should not be used in method implementation

D. Missing override keyword

Solution

1. Step 1: Check explicit implementation rules

   Explicit interface methods must not have access modifiers like public; they are implicitly private.

2. Step 2: Identify error in code

   The code uses public void IAlpha.Run(), which is invalid syntax for explicit implementation.

3. Final Answer:

   Explicit interface method cannot have public modifier -> Option A

4. Quick Check:

   Explicit methods = no public keyword [OK]

Hint: Remove public from explicit interface methods [OK]

Common Mistakes:

• Adding public modifier to explicit methods
• Confusing explicit with normal method override
• Forgetting interface name in method signature

5. Given two interfaces IX and IY both having method Process(), how can a class Worker implement both explicitly and allow calling Process() without casting?

hard

A. Use inheritance instead of interfaces

B. Implement explicit methods only, no public method needed

C. Implement only one interface explicitly and the other implicitly

D. Implement explicit methods and add a public method calling one interface method

Solution

1. Step 1: Understand explicit implementation limits

   Explicit interface methods are accessible only via interface references, not directly on class objects.

2. Step 2: Provide public method to call explicit method

   To call Process() without casting, class must have a public method that internally calls one explicit interface method.

3. Final Answer:

   Implement explicit methods and add a public method calling one interface method -> Option D

4. Quick Check:

   Public wrapper calls explicit method = direct access [OK]

Hint: Add public method calling explicit interface method [OK]

Common Mistakes:

• Expecting explicit methods callable without casting
• Implementing only one interface explicitly
• Ignoring need for public wrapper method