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

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