Skip to main content

C# : 12.0 : Primary constructor


Introduction

In C# 12.0, the introduction of the "Primary Constructor" simplifies the constructor declaration process. Before delving into this concept, let's revisit constructors.

A constructor is a special method in a class with the same name as the class itself. It's possible to have multiple constructors through a technique called constructor overloading. 

By default, if no constructors are explicitly defined, the C# compiler generates a default constructor for each class.

Now, in C# 12.0, the term "Primary Constructor" refers to a more streamlined way of declaring constructors. This feature enhances the clarity and conciseness of constructor declarations in C# code.

Lets see an simple example code, which will be known to everyone.

public class Version
{
    private int _value;
    private string _name;
    public Version(int value, string name)
    {
        _name = name;
        _value = value;
    }
    public string VersionName
    {
        get
        {
            return $"{_value} {_name}";
        }
    }
}
C#

In the above example, we have a straightforward class with two fields, _value and _name, and a parameterized constructor. 

Additionally, there's a public method that returns an immutable string value, combining the name and value.

In C# 12.0, the code can be simplified with fewer lines. The primary constructor, denoted by the class name, is introduced along with another constructor that has only one parameter. 

This showcases the elegance and brevity brought by the new primary constructor feature.

public class Version(int value, string name)
{
    public Version(int value) : this(value, "None") // call primary constructor in every  constructor
    {
    }

    public string VersionName
    {
        get
        {
            return $"{value}. {name}";
        }
    }
}
C#

The syntax in the above example might seem a bit unconventional when compared to the traditional constructor declaration. 

However, it aligns with the new features in C# , particularly the Record type, which shares a similar syntax.

Let's delve into the syntax through the provided code snippet

public record Version2(int Value, string Name)
{
    public string VersionName
    {
        get
        {
            return $"{Value} {Name}";
        }
    }
}
C#

Here created a record with similar parameters value and name addon with Version Name returning a string. 

Both record classes can be called with object instance. Whilst record Properties are created with camel case and class properties are with lowercase as usual.

var x = new Version2 (1, "Test");
Console.WriteLine (x.Value);
Console.WriteLine(x. Name);
Console.WriteLine(x. VersionName);

var y= new Version (2, "Test 2");
Console.WriteLine(y.value);
Console.WriteLine(y. name);
Console.WriteLine(y. VersionName);
C#

Primary constructor we have mutable fields. 
In record case, we have immutable properties.

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