Skip to main content

C# : Interview questions (26-30)

 

  Questions :

    • What is the "throw" keyword used for?
    • Explain the difference between "finally", "catch", and "throw" in exception handling.
    • What is the purpose of the "try" block?
    • How do you create a custom exception in C#?
    • What is the purpose of the "checked" and "unchecked" keywords?

    Answers :

    "throw" Keyword:

    The "throw" keyword in C# is used to manually throw an exception. It is typically used when a specific error condition occurs in your code that cannot be handled locally and needs to be propagated up the call stack for handling by higher-level code.

      if (age < 0) 
      {
          throw new ArgumentException("Age cannot be negative.");
      }
      

      In this example, if the age is negative, an ArgumentException is thrown with a custom error message.

      Difference between "finally", "catch", and "throw" in Exception Handling:

      • try: The "try" block encloses the code that might throw an exception. It is followed by one or more "catch" blocks to handle specific exceptions.
      • catch: The "catch" block catches and handles exceptions that are thrown within the "try" block. It specifies the type of exception to catch and provides code to handle the exception.
      • finally: The "finally" block contains code that is always executed, regardless of whether an exception occurs in the "try" block or not. It is typically used to release resources or perform cleanup operations.
      • throw: The "throw" keyword is used to manually throw an exception from within the "try" block. It allows you to propagate custom exceptions or rethrow exceptions caught in "catch" blocks.

      Purpose of the "try" Block:

      The "try" block in C# is used to enclose code that might throw an exception. It allows you to handle exceptions gracefully by catching and handling them using "catch" blocks or performing cleanup operations using "finally" blocks.

      try 
      {
          // Code that might throw an exception
      }
      catch (Exception ex) 
      {
          // Handle the exception
      }
      finally 
      {
          // Cleanup code
      }
      

      In this example, the "try" block encloses code that might throw an exception, and the "catch" block handles any exceptions that occur. The "finally" block contains cleanup code that is always executed, regardless of whether an exception occurs or not.

      Creating a Custom Exception in C#:

      To create a custom exception in C#, you need to create a new class that inherits from the Exception class or one of its derived classes. You can then add custom properties or methods to the class to provide additional information about the exception.

      class MyCustomException : Exception 
      {
          public MyCustomException(string message) : base(message) 
          {
              // Constructor
          }
      }
      

      In this example, the MyCustomException class inherits from the Exception class and provides a custom constructor to initialize the exception with a custom message.

      Purpose of the "checked" and "unchecked" Keywords:

      • checked: The "checked" keyword in C# is used to explicitly enable overflow checking for arithmetic operations, ensuring that arithmetic overflow exceptions are thrown if an overflow occurs.
      • unchecked: The "unchecked" keyword is used to explicitly disable overflow checking for arithmetic operations, allowing arithmetic overflow to occur without throwing exceptions.
      int x = int.MaxValue;
      int y = 1;
      int z = checked(x + y); // Throws OverflowException if overflow occurs
      
      int a = int.MaxValue;
      int b = 1;
      int c = unchecked(a + b); // No exception thrown for overflow
      
      In summary, the "checked" and "unchecked" keywords provide control over how arithmetic overflow is handled in C#, allowing you to choose between throwing exceptions or allowing overflow to occur silently.

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