C# Nullable Reference Types Explained

NullReferenceException is one of the most common runtime problems in C#. Nullable reference types help the compiler identify code paths where a reference may be null before the application runs.

🔎 What Does the Feature Do?

With nullable reference types enabled, a normal reference type such as string is treated as non-null by default, while string? explicitly allows null.

string name = "Dhilip";
string? optionalName = null;

⚙️ Enable Nullable Analysis

Modern .NET projects can enable nullable analysis in the project file:

<PropertyGroup>
    <Nullable>enable</Nullable>
</PropertyGroup>

The compiler can then warn when a possibly null value is assigned or dereferenced unsafely.

⚠️ A Common Warning

string? name = GetName();
Console.WriteLine(name.Length);

If GetName() can return null, the compiler can warn about accessing Length without checking the value.

✅ Null Checking

if (name is not null)
{
    Console.WriteLine(name.Length);
}

Another common pattern is:

Console.WriteLine(name?.Length);

The null-conditional operator safely avoids the member access when the value is null.

🛡️ The Null-Forgiving Operator

string value = possiblyNull!;

The ! tells the compiler that you believe the value is not null. It does not perform a runtime null check, so it should be used only when that assumption is justified.

🧠 Key Takeaway

Nullable reference types move many null-related mistakes from runtime failures toward compile-time warnings.

Continue with 💻 C# Tutorials for more C# articles.

🤖 AlgoLassi Assistant Have a question about this tutorial?

Ask AlgoLassi and get an answer plus the tutorials worth studying next.

Ask a question

💬 Comments

Comments will appear here when available.