User Story: Developers using C# nullable reference types can use them with more Microsoft SDKs to validate correctness of their code #43619
Description
In .NET 5, 94% of Microsoft.NetCore.App has been completed, which is the lowest layer in the shared framework and represents the set of APIs that are referenced by default by all applications types. We’ll work to get this number to 100% and we intend to maintain 100% coverage into the future.
What’s still missing are the higher layers (WPF, WinForms, ASP.NET Core) as well as the out-of-band packages (such as EFCore and several out-of-band packages from dotnet/runtime, as well as assemblies that aren't in netcoreapp but are included with aspnetcoreapp). While each is likely to be too big to be completed in .NET 6, we will start planning and making inroads for the rest of the stack and decide if we are comfortable introducing new libraries which may have no nullable annotations (e.g. mobile SDKs/Forms for .NET 6). An MVP (minimum viable product) for this, we believe (and will test) that any new libraries are annotated, moving forward nullable reference types are just part of the language, and when you decide the data type of some method parameter or return value, it's just one of the things you need to factor in, just as we need to factor in new types added in the libraries, new language features around optional parameters or params arguments and such things.
Work Items
- Developers benefit from nullable annotations throughout all netcoreapp and Windows Compat Pack libraries #41720
- Annotate Microsoft.Extensions.* assemblies for nullable reference types #43605
- Annotate EF Core for nullable reference types efcore#19007
- Update ASP.NET Core to use C# 8's nullable reference types aspnetcore#5680
- Turn Nullable on for new projects sdk#14272