Skip to main content

C# : Most used unknown Keywords

C# is a rich and versatile language with many features that make it a favourite among developers. 

While popular keywords like class, if, and foreach are well-known, there are some lesser-known yet powerful keywords that play a crucial role in specific scenarios.

 In this blog post, we'll unravel the mysteries behind these keywords with enlightening code snippets.

yield - Lazy Iteration

public IEnumerable<int> GenerateNumbers()
{
    for (int i = 0; i < 5; i++)
    {
        yield return i;
    }
}

// Usage
foreach (var number in GenerateNumbers())
{
    Console.WriteLine(number);
}

The yield keyword allows the creation of iterators in a more memory-efficient and lazy way. It's particularly useful when generating a sequence of values on-the-fly.

using - Resource Management

using (var resource = new MyDisposableResource())
{
    // Code that uses the resource
}

While using is a common keyword for handling disposable resources, its power is often overlooked. It ensures that the Dispose method of the resource is called, even if an exception is thrown within the block.

nameof - Compile-Time Safety

string propertyName = nameof(MyClass.MyProperty);

The nameof operator provides a way to get the name of a variable, type, or member at compile-time. This helps in avoiding magic strings, making code more maintainable.

async and await - Asynchronous Programming

async Task<string> FetchDataAsync()
{
    var result = await HttpClient.GetAsync("https://example.com/api/data");
    return await result.Content.ReadAsStringAsync();
}

The async and await keywords facilitate asynchronous programming, allowing the creation of responsive applications without blocking the main thread.

params - Variable Number of Arguments

void DisplayNumbers(params int[] numbers)
{
    foreach (var number in numbers)
    {
        Console.WriteLine(number);
    }
}

// Usage
DisplayNumbers(1, 2, 3, 4, 5);

The params keyword enables methods to accept a variable number of arguments of the specified type.

readonly - Immutable Fields

public class Constants
{
    public readonly int MaxValue = 100;
}

The readonly keyword ensures that a field can only be assigned a value at the time of declaration or in the constructor, making it immutable.

unsafe - Unsafe Code

unsafe void Square(int* number)
{
    *number = *number * *number;
}

// Usage
int value = 5;
Square(&value);

The unsafe keyword allows the use of pointers, enabling low-level operations. It should be used with caution due to potential security risks.

default - Default Values

int defaultInt = default;        // 0
bool defaultBool = default;      // false
string defaultString = default;  // null

The default keyword provides the default value for a given type, making code more concise and readable.

Conclusion

These lesser-known keywords might not be in the spotlight, but they play significant roles in specific scenarios, offering unique capabilities that contribute to the overall richness of the C# language.

 By exploring and understanding these keywords, developers can enhance their coding skills and make more informed design decisions. Happy coding!

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