Imagine My Surprise When Nullable Reference Types Became An Issue #30348
Description
I pay a hefty fee to Microsoft to subscribe to Visual Studio and have done so for a long time. I installed the latest creation the other day and compiled some of my old code in a new project. Imagine my surprise when the compiler complained about nullable reference types. Microsoft declined to send me a memo regarding substantial deprecations of syntax. In fact, I NEVER hear from Microsoft. The trade press sometimes mentions Microsoft when 97 security threats are discovered, many of them zero days. I am a software developer and have been for many decades. My old company took great care in documenting product changes. Of course, my old company had only thousands of customers, not more than a billion. My next employer was based in Paris. They hired "writers" who were not technical but did speak English. They conversed with developers and put words on paper. Extracting product design from their documents, if you could get through them, was impossible. Apparently, my industry, which is your industry, hates to write documentation. Writing code is so much more enjoyable. This page is good. I'm glad I found it. The error messages that Visual Studio issues when it discovers a reference type, that may or may not be null at runtime, could, but doesn't, refer to it.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: a690704d-da32-dca7-ea3e-66b84fb1d00d
- Version Independent ID: 11f314de-dd3a-362e-b2bb-d0a2133cfc7b
- Content: Nullable reference types
- Content Source: docs/csharp/nullable-references.md
- Product: dotnet-csharp
- Technology: csharp-null-safety
- GitHub Login: @BillWagner
- Microsoft Alias: wiwagn