Null-Conditional Assignment Archives

C# 14 introduces null-conditional assignment (?.=), a powerful new operator that makes handling nullable objects cleaner and safer. This feature helps developers cut down on boilerplate code, eliminate repetitive if (obj != null) checks, and write concise conditional assignments.

In this article, we’ll explore what null-conditional assignment is, how it works in real-world scenarios, and why it matters for modern C# developers.

What is Null-Conditional Assignment in C# 14?

Introduced in C# 6, the null-conditional operator (?.) allows developers to safely access members of nullable objects without risking a NullReferenceException.

C# 14 extends this by allowing assignments using the ?.= operator: Microsoft documentation for Null-conditional assignment

obj?.Property = value;

This statement assigns value to obj.Property only if obj is not null. If obj is null, the assignment is skipped gracefully.

Syntax of Null-Conditional Assignment

objectReference?.Member = value;

Explanation of each part in syntax

objectReference → the nullable object you’re working with.
?.= → the new operator introduced in C# 14.
Member → property or field to assign if not null.
value → the new value you want to assign.

Assigning to an Object Property

When the entire object is null, the null-conditional assignment in C# 14 ensures no exception is thrown. Instead, the operation is skipped gracefully, making your code safer and more reliable without the need for extra null checks.

Person? person = null;
person?.Name = "Jignesh Kumar";  // No exception thrown

Null-Conditional Assignment vs Traditional Null Check in C#

Traditional Null Check (Before C# 14)

Person person = new Person();
if (person != null)
{
    person.Name = "Jignesh Kumar";
}

Requires explicit if condition
More lines of code
Easy to forget in multiple assignments

Using Null-Conditional Assignment in C# 14 (After)

person?.Name = "Jignesh Kumar";

No explicit null check needed
Cleaner, one-line assignment
Prevents NullReferenceException automatically

Null-Conditional Compound Assignment

Traditional Null Check for Compound Assignment (Before C# 14)

Dictionary<string, int>? scores = null;

if (scores != null)
{
    scores["Math"] += 10;
}

Requires explicit null check validation
More lines of code for a simple operation
Easy to repeat across multiple score updates

After C# 14 – Using Null-Conditional Assignment

Dictionary<string, int>? scores = null;

scores?["Math"] += 10;  // Safe even if scores is null

No explicit null check
Clean, single-line update
Safely ignored if scores is null
Prevents NullReferenceException automatically

With the introduction of null-conditional assignment in C# 14, updating values in dictionaries, lists, or other collections is now safer and more concise, particularly when working with objects that may not be initialized.

Why Null-Conditional Assignment Matters

Write Cleaner Code – Avoids verbose null-checking conditions.
Ensure Safer Execution – Prevents NullReferenceException automatically.
Improved Readability – Intent is clear: “Assign only if not null.”
Supports Compound Operations – Makes updating values much simpler.

Summary

In this article, I’ve covered the C# 14 feature null-conditional assignment (?.=), a smart way to manage nullable objects without repetitive if checks. It helps write cleaner, safer, and more readable code while avoiding NullReferenceException. With support for compound operations like +=, updating collections and properties becomes effortless. A simple yet powerful enhancement for every modern C# developer.

🔗 Explore More from My Writing

💡 If this content helped you, do me a small favor:
👉 Repost & share with your network so more developers can benefit.
👉 Comment below with your thoughts — I’d love to hear how you approach these topics.

Together, we can share knowledge, grow as developers, and build cleaner .NET codebases 💻✨