Skip to main content

C# : Interview questions (11-15)


  Questions :

  • What is inheritance in C#?
  • Explain the concept of method overloading.
  • What is method overriding?
  • What is an abstract class in C#?
  • What is an interface?

Answers :

Inheritance in C#:

Inheritance is a fundamental feature of object-oriented programming (OOP) that allows a class (called a subclass or derived class) to inherit properties and behaviors from another class (called a superclass or base class). In C#, inheritance is implemented using the : symbol followed by the name of the base class.

    class Animal // Base class
    {
        public void Eat() 
        {
            Console.WriteLine("Animal is eating...");
        }
    }
    
    class Dog : Animal // Derived class inheriting from Animal
    {
        public void Bark() 
        {
            Console.WriteLine("Dog is barking...");
        }
    }
    

    In this example, the Dog class inherits the Eat method from the Animal class, allowing instances of Dog to both eat and bark.

    Method Overloading:

    Method overloading is a feature in C# that enables a class to have multiple methods with the same name but different parameter lists within the same scope. The parameters may differ in number, type, or both. This allows for flexibility and code organization.

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

    Here, the Add method is overloaded with two different parameter types (int and double), allowing the calculator class to handle both integer and floating-point addition.

    Method Overriding:

    Method overriding is a concept in inheritance that allows a derived class to provide a specific implementation for a method that is already defined in its base class. To override a method, the method in the derived class must have the same name, return type, and parameters as the method in the base class, and it must be marked with the override keyword.

    class Animal 
    {
        public virtual void MakeSound() 
        {
            Console.WriteLine("Animal is making a sound...");
        }
    }
    
    class Dog : Animal 
    {
        public override void MakeSound() 
        {
            Console.WriteLine("Dog is barking...");
        }
    }
    

    In this example, the MakeSound method is overridden in the Dog class to provide a specific implementation for the sound a dog makes.

    Abstract Class in C#:

    An abstract class in C# is a class that cannot be instantiated directly and may contain abstract methods, which are methods without a body. Abstract classes are meant to serve as base classes for other classes and define a common interface that derived classes must implement.

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

    In this example, Shape is an abstract class with an abstract method Draw. The Circle class inherits from Shape and provides an implementation for the Draw method.

    Interface:

    An interface in C# is a reference type that defines a contract for classes to implement. It contains method signatures, properties, events, and indexers without any implementation. Classes that implement an interface must provide concrete implementations for all members defined by the interface.

    interface IShape 
    {
        void Draw();
    }
    
    class Circle : IShape 
    {
        public void Draw() 
        {
            Console.WriteLine("Drawing a circle...");
        }
    }
    

    In this example, IShape is an interface with a single method Draw. The Circle class implements the IShape interface by providing an implementation for the Draw method.

    These concepts are foundational to understanding and building object-oriented applications in C#.

    C# : Interview questions (16-20)

    Comments

    Popular posts from this blog

    Implementing and Integrating RabbitMQ in .NET Core Application: Shopping Cart and Order API

    RabbitMQ is a robust message broker that enables communication between services in a decoupled, reliable manner. In this guide, we’ll implement RabbitMQ in a .NET Core application to connect two microservices: Shopping Cart API (Producer) and Order API (Consumer). 1. Prerequisites Install RabbitMQ locally or on a server. Default Management UI: http://localhost:15672 Default Credentials: guest/guest Install the RabbitMQ.Client package for .NET: dotnet add package RabbitMQ.Client 2. Architecture Overview Shopping Cart API (Producer): Sends a message when a user places an order. RabbitMQ : Acts as the broker to hold the message. Order API (Consumer): Receives the message and processes the order. 3. RabbitMQ Producer: Shopping Cart API Step 1: Install RabbitMQ.Client Ensure the RabbitMQ client library is installed: dotnet add package RabbitMQ.Client Step 2: Create the Producer Service Add a RabbitMQProducer class to send messages. RabbitMQProducer.cs : using RabbitMQ.Client; usin...

    How Does My .NET Core Application Build Once and Run Everywhere?

    One of the most powerful features of .NET Core is its cross-platform nature. Unlike the traditional .NET Framework, which was limited to Windows, .NET Core allows you to build your application once and run it on Windows , Linux , or macOS . This makes it an excellent choice for modern, scalable, and portable applications. In this blog, we’ll explore how .NET Core achieves this, the underlying architecture, and how you can leverage it to make your applications truly cross-platform. Key Features of .NET Core for Cross-Platform Development Platform Independence : .NET Core Runtime is available for multiple platforms (Windows, Linux, macOS). Applications can run seamlessly without platform-specific adjustments. Build Once, Run Anywhere : Compile your code once and deploy it on any OS with minimal effort. Self-Contained Deployment : .NET Core apps can include the runtime in the deployment package, making them independent of the host system's installed runtime. Standardized Libraries ...

    Clean Architecture: What It Is and How It Differs from Microservices

    In the tech world, buzzwords like   Clean Architecture   and   Microservices   often dominate discussions about building scalable, maintainable applications. But what exactly is Clean Architecture? How does it compare to Microservices? And most importantly, is it more efficient? Let’s break it all down, from understanding the core principles of Clean Architecture to comparing it with Microservices. By the end of this blog, you’ll know when to use each and why Clean Architecture might just be the silent hero your projects need. What is Clean Architecture? Clean Architecture  is a design paradigm introduced by Robert C. Martin (Uncle Bob) in his book  Clean Architecture: A Craftsman’s Guide to Software Structure and Design . It’s an evolution of layered architecture, focusing on organizing code in a way that makes it  flexible ,  testable , and  easy to maintain . Core Principles of Clean Architecture Dependency Inversion : High-level modules s...