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

From the creator

Isn't `null` the bane of many of a developer's life? Working with nullable data has always required some amount of understanding this third state of data. Recently, Microsoft introduced Nullable Reference Types to .NET developers and for many a long-term C# developer, the change was daunting. In recent iterations, Nullable Reference Types are now the default for new projects. But once you understand the reason to use Nullability, you'll see how it can simply your code and have to use less safeguards around your code. Instead of turning it off, let me show you why Nullable Reference Types exist and how they could make your code better. 🎥 See more from .NET Conf: https://aka.ms/dotnetconf-playlist 🔗 Links: .NET 10 — The most intelligent and unified .NET yet: https://aka.ms/dotnet10/ .NET Aspire 13 — Simplified orchestration for cloud-native apps: https://aka.ms/aspire13/announcement ASP.NET Core 10 — Modern, secure, and full-stack web development: https://aka.ms/asp/dotnet/2025 .NET MAUI 10 — Build beautiful apps on every platform: https://aka.ms/dotnet/maui/2025 C# 14 — A more expressive and productive language: https://aka.ms/csharp14/announcement/2025 F# 10 — Safer, faster, and more functional than ever: https://aka.ms/fsharp10/2025/announcement Visual Studio 2026 — Faster, smarter, and built for the future: https://aka.ms/visualstudio2026/announcement 🎙️ Featuring: Shawn Wildermuth (@shawnwildermuth) Connect with .NET: Blog: https://aka.ms/dotnet/blog Twitter: https

Published 2025-11-14 · Watch on YouTube ↗
Availability and playback restrictions are controlled by the original channel.