Is it that bad once you are on .NET Core? Asking as someone still on Framework.
Framework -> Core ofcourse is breaking, what did you expect when going cross platform and totally rearchitected?
I am not saying .net core is bad, just that the migration is a lot of work. And you need to disable all sorts of compiler warnings unless you are ready to rewrite pretty much all your code to make it nullable ref type friendly. And some day those warnings will be errors.
Not really. Just disable nullability checking — you can do it project-wide by removing the Nullable tag from your .csproj, and you can continue ignoring nullability.
> And some day those warnings will be errors.
[citation needed]. A lot of code is written without nullability in mind. That includes the .NET Core BCL, AFAIK.
The BCL was completely annotated with NRTs for the .NET 7 release, minus some #nullable disable spots.