Remove package references to runtime and ref pack files when targeting .NET 6+.

[AraHaan]

In .NET 6+ minimize network load on restore by using the ones from the ref and runtime packs over the package versions.

[AraHaan]

Sad the CI does not have the .NET 6 SDK it looks like.

[JRahnama]

@AraHaan we are adding net6 to driver build pretty soon. Maybe in preview 2 release. That will unblock some other features we are trying to add.

[AraHaan]

Sad, too bad it cant be done right before the preview 1 release so we can see some simple configuration changes like this make their way into preview 1 as well (also so that way I do not have to wait long to notice the changes I made getting pulled into my codebase as well) thanks to having this as an indirect dependency from EFCore.

[AraHaan]

This will need to be made to not reference the nuget package versions of the assemblies in the normal runtime and ref pack files as well when targeting .NET 6+ (will require PR to their repo).

[AraHaan]

@JRahnama so maybe sometime in April. Mind adding this to the p2 or p3 milestone then so when it happens this can get merged when it's unblocked?

[JRahnama]

@AraHaan I was going through this PR and made some testing. TargetFrameworkIdentifier and similar names apparently wont work when multi frame works are being specified. Netcoreapp 3.1 is going out of support by end of this year and we are working on adding net6 builds to the driver. Just bear with us for the moment. Thanks for you patience.

[AraHaan]

So would it be ok to eventually remove .NET Core 3.1 from SqlClient when that happens (to force users to update to .NET 6+) if they are not targeting .NET Framework using SqlClient?

[AraHaan]

@JRahnama eta on when adding .NET 6 might be completed?

[JRahnama]

@JRahnama eta on when adding .NET 6 might be completed?

We will resume working on this after first GA at the end of May. Since 3.1 EOL is Dec 3, 2022.

[AraHaan]

Sad that the .NET 6 SDK (at least) cant be installed before then as it can be used to build the older TFMs still.

[AraHaan]

I have almost got the codebase to build for .NET 6, I had to remove TargetGroup as for some reason it does not work well with TargetFrameworkIdentifier.

After that I had to work around errors from the usage of:

• WebClient (Suppress for now)
• CAS (Avoid usage in .NET 6+ using #if)
• CER (Avoid usage in .NET 6+ using #if)
• Suppress CA1416 in .editorconfig for files with the pattern *.Windows.cs as they were false positives (at least I hope they were).

And with that the codebase now builds with .NET 6 added (locally).

[AraHaan]

Microsoft.IdentityModel.Tokens (dependency of this) seems to needlessly depend on the Microsoft.CSharp, and the System.Security.Cryptography.Cng package.

When these 2 are fixed that would be a big help to me and others.

[ErikEJ]

@JRahnama This PR seems obsolete now?

[JRahnama]

Closing this PR as it is obsolete now.