Target .NET 6.0

[bricelam]

Rationale:

• Unlike .NET Standard, older versions of .NET don't enable any additional platforms.
• We moved to .NET 5 because it enables the same platforms as .NET Standard 2.1, but with additional features (like savepoint APIs in ADO.NET) that we can leverage.
• .NET 5 will go out of support three months after .NET 6 ships anyway.
• The migration from .NET 5 to 6 should be pretty seamless

[ErikEJ]

What is the milestone for this?

[roji]

@ErikEJ this should apply for 6.0.0-preview6. Preview5 will still target net5.0.

[vslee]

One downside to doing this in the preview phase is that it makes it a little more difficult for people to test the previews. Before, ppl could just update the NuGet from 5.0 to a 6.0.0-preview and try out the new EF Core. Now, it also requires installing a preview .NET Core.

[roji]

@vslee that's true - we discussed this when making the decision to target net6.0. At the end of the day, we're starting to near the end of the 6.0 development cycle, and at some point we were bound to do this change. Hopefully installing a 6.0 dotnet SDK preview isn't that much of an effort.