Your clients are lying! Adventure with leaky .NET
summary
Claim: C# nullable reference types are only compile‑time warnings so runtime deserialization still produces invalid objects and hidden NullReferenceExceptions. Demonstration shows JSON-to-object pitfalls, a proof‑of‑concept validator using reflection and libraries like NullabilityInfo and nullability reflection, and a pragmatic stack: enable warnings-as-errors, use the csharp extensions analyzers, adopt strong‑typed IDs and union‑style modeling to get exhaustive switches and fail‑fast behavior. Practical fixes and migration strategies for existing .NET codebases are given.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:19What Is a Null Pointer Exception and How Do We Fix It
- 4:39Conclusion
- 7:11Nullable Types
- 9:14Difference between the Dotnet 5 Version and Dotnet6 Version
- 9:57Weather Forecast
- 15:18How Can We Help Ourselves
- 19:13Initialization
- 27:48Json Converters
- 30:08Oop Object Oriented Programming
- 37:00Is It Possible To Have a Tanked Union in C Sharp
related talks
49mFixing the Billion Dollar Mistake
01h 09mRefraction of Reality: Dynamic Validation with Static Types
44mThe long good-bye to NPE
40mBugs?! Where do they come from?
46mAre you writing valuable tests (2025 edition)?
05mDetecting Programs That Rely on Undefined Behavior
26mUndefined Behavior in 2017 (part 2 of 2)
01h 01mBreaking Your Code in New and Exciting Ways