3 ms·
> Not breaking your users used to be a laudable goal of the .net team. I miss it Is it that bad once you are on .NET Core? Asking as someone still on Framework
by jve 4y ago
> Not breaking your users used to be a laudable goal of the .net team. I miss it
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?
- cm2187 4y agoI am sure cross platform is useful to some users but not to me. So to me it's all breaking changes for little benefits. 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.
- Kwpolska 4y ago> 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. 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.
- Hawxy 4y ago> That includes the .NET Core BCL, AFAIK. The BCL was completely annotated with NRTs for the .NET 7 release, minus some #nullable disable spots.
- simooooo 4y agoIt’s fine while on core. Maybe adjusted the app setup 2-3 times, fairly trivial stuff, an hour or so in the last year