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

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

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