dotnet presents a session on the practical reasons for using Nullable Reference Types in .NET, showing how this feature enhances code safety and readability.

Nullable Reference Types: It's Actually About Non-Nullable Reference Types

Overview

Nullable Reference Types, recently introduced to .NET and now enabled by default in new C# projects, are designed to help developers manage the presence of null in reference types more effectively. This session examines the motivation behind the feature, common misconceptions, and practical benefits.

Why Nullable Reference Types?

• Historical Challenge: Null references have long complicated codebases, requiring extensive safeguards and checks.
• The Shift: Nullable Reference Types enforce clear intent in your code—whether a reference type may be null or is guaranteed to always contain a value.
• Default Behavior: In modern .NET project templates, Nullable Reference Types are enabled by default, encouraging safer code from the outset.

Benefits for Developers

• Safer Code: Explicitly define variables as nullable or non-nullable, reducing the risk of null reference exceptions.
• Simplified Maintenance: Improve code readability and maintain fewer null-checks throughout your project.
• Compiler Guidance: Leverage compiler warnings to catch potential issues at build time rather than at runtime.

Best Practices

• Don't disable Nullable Reference Types—use them to improve code clarity.
• Use the ? annotation for references that can be null, otherwise declare references as non-nullable.
• Respond to compiler warnings, refactoring code where necessary to fix nullability issues.

Further Learning

Watch more .NET Conf 2025 videos at YouTube .NET Conf Playlist.