Unlike value types which always have a default actual value (e.g. 0 for int), reference types by default can be null indicating no value at all.
This can cause NullReferenceExceptions at runtime if the developer forgets to check for null before accessing members of the object.
C# 8.0 introduces an option for the compiler to switch into nullability checking mode and warn of potential issues.
To enable this mode add the following to your .csproj file:
xml
<PropertyGroup>
<Nullable>enable</Nullable>
</PropertyGroup>The various options are:
enable: Enable nullability checking for all reference typesdisable: Disable nullability checking for all reference typeswarnings: Enable nullability checking for all reference types but only warn on violationsannotations: Enable nullability checking for all reference types and warn on violations except when the value is assigned to a non-nullable variable
Code
C#
// With nullable context enabled
string name = GetName(); // Non-nullable, compiler warns if null is assigned
string? nickname = GetAlias(); // Explicitly nullable
if (nickname != null)
Console.WriteLine(nickname.Length); // No warning, compiler tracks null stateC#
// Without nullable context
string name = GetName(); // Could be null with no warning
string nickname = GetAlias(); // Could also be null with no warning
if (nickname != null)
Console.WriteLine(nickname.Length); // Works but compiler offered no helpNotes
- Not to be confused with nullable value types which allow value types to be
null(e.g.int?).