Skip to main content

C# : Interview questions (51-55)

 

 Questions :

    • What is the purpose of the "using" directive in C#?
    • How do you define a constant in C#?
    • What is the purpose of the "readonly" keyword in C#?
    • Explain the use of the "volatile" keyword in C#.
    • What is a property in C#?

    Answers :

    1. Purpose of the "using" Directive in C#:

    The "using" directive in C# serves two main purposes:

    • Namespace Importing: It allows you to import namespaces into your code file, enabling you to use types (classes, interfaces, enums, etc.) defined within those namespaces without fully qualifying their names.

    using System; // Importing the System namespace
    
    class Program 
    {
        static void Main() 
        {
            Console.WriteLine("Hello, World!"); // Using Console class without fully qualifying its name
        }
    }
    
    • Resource Management: When used with disposable types (types that implement the IDisposable interface), the "using" directive ensures that the Dispose method of the object is called when the object goes out of scope, thereby releasing any unmanaged resources held by the object.
    using (var stream = new FileStream("file.txt", FileMode.Open)) 
    {
        // Read from the file...
    } // Dispose method of the stream is automatically called when it goes out of scope
    

    2. Defining a Constant in C#:

    Constants in C# are defined using the "const" keyword and must be assigned a value at the time of declaration. Constants are immutable and their values cannot be changed once defined.

    public class MathConstants 
    {
        public const double Pi = 3.14159;
    }
    

    In this example, "Pi" is a constant field of the MathConstants class, which holds the value of the mathematical constant π.

    3. Purpose of the "readonly" Keyword in C#:

    The "readonly" keyword in C# is used to declare fields that can only be assigned a value once, either at the time of declaration or within a constructor of the class. Once assigned, the value of a "readonly" field cannot be changed for the lifetime of the object.

    public class Configuration 
    {
        public readonly int MaxConnections;
    
        public Configuration(int maxConnections) 
        {
            MaxConnections = maxConnections; // Assign value within constructor
        }
    }
    

    In this example, "MaxConnections" is a readonly field of the Configuration class, which can only be assigned a value once, either at the time of object creation or within the constructor.

    4. Use of the "volatile" Keyword in C#:

    The "volatile" keyword in C# is used to indicate that a field may be modified by multiple threads that are executing concurrently. It ensures that operations on the field are atomic and prevents compiler optimizations that might reorder or cache reads and writes to the field.

    public class SharedData 
    {
        public volatile bool IsRunning;
    }
    

    In this example, "IsRunning" is a volatile field of the SharedData class, which may be accessed and modified by multiple threads simultaneously without causing data inconsistency issues.

    5. Property in C#:

    A property in C# is a member of a class that provides a flexible way to read, write, or compute the value of a private field. Properties encapsulate fields by exposing them through getter and setter methods, allowing controlled access to the underlying data.

    public class Person 
    {
        private string name;
    
        public string Name 
        {
            get { return name; }
            set { name = value; }
        }
    }
    
    In this example, "Name" is a property of the Person class that encapsulates access to the private field "name". The "get" accessor retrieves the value of the field, while the "set" accessor assigns a new value to the field. Properties provide a more controlled and flexible way to access and manipulate data within a class.

    Comments

    Popular posts from this blog

    Optional Parameters in C# — Writing Flexible and Clean Methods

    Hello, .NET developers! 👋 How often have you created multiple method overloads just to handle slightly different cases? Maybe one method accepts two parameters, another three, and one more adds a flag for debugging? That’s a lot of code duplication for something that can be solved beautifully with optional parameters . Optional parameters in C# let you define default values for method arguments. When a caller doesn’t pass a value, the compiler automatically substitutes the default. This feature helps keep your APIs simple, readable, and maintainable. 🎥 Explore more on YouTube : DotNet Full Stack Dev Understanding Optional Parameters Optional parameters are defined by assigning default values in the method signature. When calling the method, you can omit those parameters if you’re okay with the defaults. Example public class Logger { public void Log(string message, string level = "INFO", bool writeToFile = false) ...

    .NET 10: Your Ultimate Guide to the Coolest New Features (with Real-World Goodies!)

     Hey .NET warriors! 🤓 Are you ready to explore the latest and greatest features that .NET 10 and C# 14 bring to the table? Whether you're a seasoned developer or just starting out, this guide will show you how .NET 10 makes your apps faster, safer, and more productive — with real-world examples to boot! So grab your coffee ☕️ and let’s dive into the awesome . 💪 1️⃣ JIT Compiler Superpowers — Lightning-Fast Apps .NET 10 is all about speed . The Just-In-Time (JIT) compiler has been turbocharged with: Stack Allocation for Small Arrays 🗂️ Think fewer heap allocations, less garbage collection, and blazing-fast performance . Better Code Layout 🔥 Hot code paths are now smarter, meaning faster method calls and fewer CPU cache misses. 💡 Why you care: Your APIs, desktop apps, and services now respond quicker — giving users a snappy experience . 2️⃣ Say Hello to C# 14 — More Power in Your Syntax .NET 10 ships with C# 14 , and it’s packed with developer goodies: Field-Bac...

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