Skip to main content

Extension Methods

Extension methods allow developers to add new methods to existing types (classes, interfaces, structs) without modifying the original source code or creating a new derived type.

A quick metaphor

Imagine you've bought a new basic bicycle. It's nice, but wouldn't it be cool if you could add a basket without welding or making permanent changes? That's what Extension Methods in C# are like!

So, what are Extension Methods?

    They let you add new methods (or features) to existing classes (like our bicycle) without changing their original code.

The Creation process

Make a static method (a method that belongs to a class, not an object) inside a static class (a class that can't be instantiated).
The first parameter of this method uses the this keyword and mentions the type (or class) you want to add a method to.

 The Rules

It must be defined in a static class.
It must be a static method.
The first parameter specifies the type you're extending, prefixed with the this keyword.

Quick example:

For instance, in C#, strings don't have a built-in method to count words. But with Extension Methods, you can add one:

public static class StringHelpers

{

    public static int CountWords(this string phrase)

    {

        return phrase.Split(new char[] { ' ', '.', '?' }, StringSplitOptions.RemoveEmptyEntries).Length;

    }

}

 

Output:

string myText = "C# is fun!";

int totalWords = myText.CountWords();  // This gives 3.

 

Why Use Extension Methods?

    Readability: They can make the code more intuitive and readable.
    Reusable Code: Common utility functions can be turned into extension methods for reuse across projects.
    Extending Sealed Classes: They allow adding methods to sealed classes or types from third-party libraries.

Important Points to Consider

    No Access to Private Members: Extension methods can't access private members of the type they're extending.
    Discoverability: New team members might find it challenging to discover extension methods compared to traditional methods.
    Overuse: Avoid turning every utility function into an extension method. Use them when it genuinely enhances code readability or utility. 

Real-world Applications

    LINQ: Language Integrated Query (LINQ) extensively uses extension methods. For instance, methods like Where or Select are extension methods provided for collections.
    Serialization/Deserialization: Convert objects to JSON or XML and vice-versa without cluttering the original class.

The code samples can be found at https://github.com/oneananda/C_Sharp_Examples/tree/main/ExtensionMethods


 

Comments

Popular posts from this blog

Using of global variables in C# - Drawbacks & Solutions

How using global variables can have implications on the design, maintainability, and test-ability of C# code: Harder to understand and reason about the code:       class Program     {         public static int globalCounter = 0;         static void Main()         {             globalCounter++;             Console.WriteLine(globalCounter);         }     }   In this example, the global variable globalCounter is accessible from anywhere in the program, including the Main method. It's not clear where the value of the globalCounter is updated, it could be updated in other methods or classes, making it harder to trace the flow of data and understand the source of bugs.   More prone to errors:       class Program     {         public static string globalString;         static void Main()         {             globalString = "Hello" ;             Method1();             Method2();         }         static void Method1()         {

Task Parallel Library (TPL) and Akka.NET Alternatives

Task Parallel Library (TPL) and Akka.NET are among the most commonly used libraries for parallel and concurrent programming in the .NET ecosystem. However, there are also several other options available, depending on your specific needs: Parallel Language Integrated Query (PLINQ) is a parallel programming feature of .NET that provides an easy and efficient way to perform operations on collections in parallel. LINQ (Language Integrated Query) is a powerful feature in .NET that allows developers to work with data in a more declarative and language-integrated manner. While LINQ queries are inherently sequential, PLINQ extends LINQ by providing parallel versions of the query operators, allowing some queries to execute faster by utilizing multiple processors or cores on a machine. PLINQ is great when you are working with large collections where operations might be CPU-intensive or I/O-bound and could potentially be sped up by parallel execution. Here is a simple example of a PLI

SOLID Principles with Real World examples in C#

  SOLID Principles with Real World examples in C#   SOLID principles are formed by using S Single Responsibility Principles (SRP) O Open Closed Principle (OCP) L Liskov’s Substitution Principle (LCP) I Interface Segregation Principle (ISP) D Dependency Inversion Principle (DIP)   S Single Responsibility Principles (SRP) There should never be more than one reason for a class to change, to be precise one class should have only one responsibility Single Responsibility Principles (SRP) Real world example, A perfect match for SRP is Microservices , a Microservice will not contain functionalities other than the one it is designated to do,  Example ·                   Order Processing Service, ·                   Shipment Management Service, ·                   User Authentication Service, ·                   Catalogue List Service       class OrderProcessor     {         public void Process(Order order)         {             // Check inven