Skip to main content

C# : Interview questions (96-100)

 

Questions:

  • How do you invoke a method using reflection in C#?
  • What is the purpose of the "dynamic" keyword in C#?
  • How do you work with dynamic types in C#?
  • What is the "var" keyword in C#?
  • What is the purpose of the "out" keyword in C#?
Answers:

1. Invoking a Method Using Reflection in C#:

To invoke a method using reflection in C#, you typically follow these steps:

  • Get the Type of the class that contains the method using typeof or GetType().
  • Use GetMethod to obtain a MethodInfo object representing the method.
  • Optionally, use GetParameters to get information about the method's parameters.
  • Invoke the method using Invoke on an instance (for instance methods) or null (for static methods), passing in any required parameters.

using System;
using System.Reflection;

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

public class Program
{
    public static void Main()
    {
        Type type = typeof(Calculator);
        object instance = Activator.CreateInstance(type);

        MethodInfo methodInfo = type.GetMethod("Add");
        object[] parameters = { 3, 5 };
        int result = (int)methodInfo.Invoke(instance, parameters);

        Console.WriteLine($"Result of Add method: {result}"); // Output: Result of Add method: 8
    }
}

In this example, MethodInfo.Invoke is used to dynamically invoke the Add method of the Calculator class with parameters 3 and 5.

2. Purpose of the "dynamic" Keyword in C#:

The dynamic keyword in C# enables late binding, allowing you to work with objects in a more flexible and less restrictive manner at runtime. It bypasses static type checking and enables operations that might not be known at compile-time.

3. Working with Dynamic Types in C#:

When you declare a variable as dynamic, the compiler defers type checking until runtime, providing more flexibility in handling objects whose types are not known until runtime or that have properties/methods determined dynamically.

dynamic dynamicVariable = 10;
dynamicVariable = "Hello";

Console.WriteLine(dynamicVariable); // Output: Hello

In this example, dynamicVariable can hold both int and string values, and the compiler resolves the actual type at runtime.

4. The "var" Keyword in C#:

The var keyword in C# is used to declare implicitly typed local variables. The type of the variable is inferred by the compiler based on the assigned value at compile-time.

var number = 10; // Compiler infers int
var message = "Hello"; // Compiler infers string

Console.WriteLine(number); // Output: 10
Console.WriteLine(message); // Output: Hello

Using var reduces redundancy in code without sacrificing type safety, as the compiler still enforces type rules.

5. Purpose of the "out" Keyword in C#:

The out keyword in C# is used in method parameters to indicate that the parameter is passed by reference and is expected to be initialized by the method. It allows a method to return multiple values.

public void Divide(int dividend, int divisor, out int quotient, out int remainder)
{
    quotient = dividend / divisor;
    remainder = dividend % divisor;
}

// Usage
int dividend = 10, divisor = 3;
int resultQuotient, resultRemainder;
Divide(dividend, divisor, out resultQuotient, out resultRemainder);

Console.WriteLine($"Quotient: {resultQuotient}, Remainder: {resultRemainder}"); // Output: Quotient: 3, Remainder: 1

In this example, the Divide method uses out parameters to return both the quotient and remainder of dividing dividend by divisor.

These explanations and examples should provide a clear understanding of invoking methods using reflection, using the dynamic keyword, working with dynamic types, the var keyword for implicitly typed variables, and the out keyword for method parameters in C#.

C# : Interview questions (101-105)

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