Skip to main content

C# : Interview questions (16-20)

 

  Questions :

  • Can you implement multiple interfaces in C#?
  • What is a namespace in C#?
  • Explain the concept of encapsulation.
  • What is a constructor in C#?
  • Differentiate between a class and an object.

Answers :

Implementing Multiple Interfaces in C#:

Yes, C# allows a class to implement multiple interfaces, enabling it to define behaviour specified by each interface. Multiple interfaces can be separated by commas in the class declaration.

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

    In this example, the Circle class implements both the IShape and IMovable interfaces, providing concrete implementations for the Draw and Move methods defined by each interface.

    Namespace in C#:

    A namespace in C# is a way to organize and group related classes, interfaces, enumerations, and other types into logical containers. It helps prevent naming conflicts and makes it easier to manage and maintain large codebases.

    namespace MyNamespace 
    {
        class MyClass 
        {
            // Class members
        }
    }
    

    In this example, MyClass is defined within the MyNamespace namespace. To use classes defined in a namespace, you can either fully qualify the name (MyNamespace.MyClass) or use a using directive to import the namespace (using MyNamespace;).

    Encapsulation:

    Encapsulation is a fundamental concept in object-oriented programming that involves bundling data (attributes or fields) and methods (functions or procedures) that operate on the data into a single unit known as a class. It hides the internal state of an object and restricts access to it through public methods, thereby promoting data abstraction and information hiding.


    class Car 
    {
        private string model;
    
        public string Model 
        {
            get { return model; }
            set { model = value; }
        }
    
        public void Start() 
        {
            // Start the car
        }
    
        public void Stop() 
        {
            // Stop the car
        }
    }
    

    In this example, model is encapsulated within the Car class, and access to it is controlled through public getter and setter methods (Model). This allows for controlled manipulation of the model attribute and ensures data integrity.

    Constructor in C#:

    A constructor in C# is a special method that is automatically called when an instance of a class is created. It is used to initialize the object's state, allocate resources, and perform any other setup tasks necessary for the object to function properly.

    class Person 
    {
        private string name;
    
        public Person(string name) 
        {
            this.name = name;
        }
    
        public void Display() 
        {
            Console.WriteLine("Name: " + name);
        }
    }
    

    In this example, Person class has a constructor that takes a name parameter and initializes the name field. When an instance of Person is created, the constructor is automatically invoked to initialize the object.

    5. Class vs. Object:

    • Class: A class in C# is a blueprint or template that defines the structure and behaviour of objects. It encapsulates data (attributes) and methods (functions) that operate on the data. Classes serve as a blueprint for creating multiple instances of objects with similar characteristics.

    • Object: An object in C# is an instance of a class. It represents a real-world entity or concept and encapsulates its own state (data) and behaviour (methods). Objects are created using constructors and can interact with each other by invoking methods and accessing properties defined by their class.

    In summary, classes define the structure and behaviour of objects, while objects represent instances of classes with specific states and behaviours.

    C# : Interview questions (21-25)

    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...

    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...

    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 ...