DEV Community: Ramkumar Radhakrishnan

Senior C#/.NET Developer Learning Plan. Day - 01.

Ramkumar Radhakrishnan — Sat, 16 Aug 2025 18:13:45 +0000

Senior C#/.NET Developer Learning Plan
Duration: 12 Weeks (60 Sessions) | Daily Commitment: 1 Hour | Schedule: Monday to Friday

Day - 01

Topics - C# 10-12 Features

Global Using Directives *Explanation *- This feature allows you to declare common namespaces globally, eliminating the need to add using statements in every file.

Real-world use: In large projects, many files might use the same set of namespaces (e.g., System, System.Collections.Generic, System.Linq). Global usings can significantly reduce the boilerplate code at the top of each file, making code cleaner and more readable.

Code Samples.

GlobalUsing.cs

global using System;
global using System.Collections.Generic;
global using System.Linq;

Program.cs

public class Product
{
    public string Name { get; set; }
    public decimal Price { get; set; }
}

public class Order
{
    public List<Product> Products { get; set; } = new();

    public decimal TotalPrice => Products.Sum(p => p.Price);
    public void AddProduct(Product product)
    {
        Products.Add(product);
    }

    public void RemoveProduct(Product product)
    {
        Products.Remove(product);
    }

    public void ClearProducts()
    {
        Products.Clear();
    }

    public override string ToString()
    {
        return $"Order with {Products.Count} products, Total Price: {TotalPrice:C}";
    }
}

public class Program
{
    public static void Main(string[] args)
    {
        Order order = new();
        order.AddProduct(new Product { Name = "Apple", Price = 1.20m });
        order.AddProduct(new Product { Name = "Banana", Price = 0.80m });
        Console.WriteLine(order.ToString());
    }
}

C# 14 Fav Feature

Ramkumar Radhakrishnan — Mon, 11 Aug 2025 09:26:47 +0000

Recently I had a chance in reading C# 14 new features. You can refer here -

If you dont find a time, and you want to pick one update which can save your coding a much extend. Here it is.

Null-conditional assignment

Previously, we had to check the not null before assignment as

if (customer is not null) { customer.Order = GetCurrentOrder(); }

Now it can be changed to

customer?.Order = GetCurrentOrder();

The right side of the = operator is evaluated only when the left side isn't null. If customer is null, the code doesn't call GetCurrentOrder.

26th June.

Ramkumar Radhakrishnan — Fri, 27 Jun 2025 21:10:25 +0000

Required Syntax/ keyword.

I came across ‘required’ key word in C#. Not sure which version it was introduced. But now it exists, so just used copilot to enhance my understanding on the same.

public class Person
{
 public required string Name { get; set; }
 public int Age { get; set; }
}

If you are a C# developer, u might haven't skipped properties. Now adding required before the variable makes it like you have to set the value explicitly. If it's not a required property, C# takes care of the setting default values.

var p = new Person(); // ❌ Error: Name is required
var p = new Person { Name = “Ram” , Age = 36 }; // This is correct.

This applies to fields and properties. This is different from [required] attribute.

While understanding about this, I had a doubt you can set the properties by adding parameters to the constructors. Let say,

public class Person
{
 public string Name { get; set; }
 public int Age { get; set; }
}


Person(string name)
{
  Name = name; 
}

What difference it could bring? I checked with copilot again. I could understand that,

Constructors are enforced during the compile time and required are forced only during run time.

By this type, you can evolve the code, but in case constructors we have to make sure fix during the compile time. Also, the code looks clean and neat in terms the required.

Refactoring is flexible — If I have to introduce a new parameter in the constructor, I have to makes changes all the way where all the initialization has happened but not the case with required.

Fields can grow! agreed!

But usually, developers introduce parameter constructor for the sake the sake of validation even before creation object which in case of ‘required’ is not possible.

So, in the end I am good at ‘required’ :P