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

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

C# : How can we access private method outside class

Introduction In object-oriented programming, encapsulation is a fundamental principle that restricts direct access to the internal implementation details of a class. Private methods, being part of this internal implementation, are designed to be accessible only within the confines of the class they belong to. However, there might be scenarios where you need to access a private method from outside the class. In this blog post, we'll explore several techniques to achieve this in C#. 1. Reflection: A Powerful Yet Delicate Approach Reflection is a mechanism in C# that allows inspecting and interacting with metadata about types, fields, properties, and methods. While it provides a way to access private methods, it should be used cautiously due to its potential impact on maintainability and performance. using System ; using System . Reflection ; public class MyClass { private void PrivateMethod ( ) { Console . WriteLine ( "This is a private method."...

20+ LINQ Concepts with .Net Code

LINQ   (Language Integrated Query) is one of the most powerful features in .NET, providing a unified syntax to query collections, databases, XML, and other data sources. Below are 20+ important LINQ concepts, their explanations, and code snippets to help you understand their usage. 1.  Where  (Filtering) The  Where()  method is used to filter a collection based on a given condition. var numbers = new List < int > { 1 , 2 , 3 , 4 , 5 , 6 } ; var evenNumbers = numbers . Where ( n => n % 2 == 0 ) . ToList ( ) ; // Output: [2, 4, 6] C# Copy 2.  Select  (Projection) The  Select()  method projects each element of a sequence into a new form, allowing transformation of data. var employees = new List < Employee > { /* ... */ } ; var employeeNames = employees . Select ( e => e . Name ) . ToList ( ) ; // Output: List of employee names C# Copy 3.  OrderBy  (Sorting in Ascending Order) The  Or...