Target .NET 6.0 with ef6

[ErikEJ]

No description provided.

[ErikEJ]

@bricelam What do you think? No more net3.x any more at least!

[bricelam]

Hmm, it's a breaking change, but 3.1 and 5.0 are out of support, so maybe it's acceptable. Let me see if it avoids downloading the problematic DLLs. If it does, I'll discuss it with the team.

[ErikEJ]

Looking forward to the outcome!

[ErikEJ]

@bricelam Just verified that 3.0.3 is no longer downloaded:

In artifacts\obj\ef6\project.assets.json

        "downloadDependencies": [
          {
            "name": "Microsoft.AspNetCore.App.Runtime.win-arm64",
            "version": "[6.0.23, 6.0.23]"
          },
          {
            "name": "Microsoft.NETCore.App.Runtime.win-arm64",
            "version": "[6.0.23, 6.0.23]"
          },
          {
            "name": "Microsoft.WindowsDesktop.App.Runtime.win-arm64",
            "version": "[6.0.23, 6.0.23]"
          }
        ],
        "frameworkReferences": {
          "Microsoft.NETCore.App": {
            "privateAssets": "all"
          }
        },

[ErikEJ]

@bricelam ,Did you reach a conclusion? 😉

[bricelam]

Met yesterday. We all agree it's OK to make this breaking change.

[ErikEJ]

Wauw - you made my day! 😄

[bricelam]

lol, I'm trying not to get my hopes up. Every time I think we're close to releasing, something seems to go wrong. 🤞

[bricelam]

Well, we fixed one of the issues. Two more to go... ☹️

[ErikEJ]

@bricelam Let me know if I can help

[bricelam]

One of the errors is related to dotnet/efcore#32108, so that should eventually get resolved. I'll work on resolving the remaining error.

[ErikEJ]

@David-Engel Was a 5.1.3 release with an updated Azure.Identity planned? And if so, when?

@bricelam Will adding an explicit reference fix this?

[David-Engel]

We have a MDS 5.1 hotfix release with the updated dependency scheduled for early January. It'll be 5.1.4.

[ErikEJ]

@David-Engel Thank you so much!

[bricelam]

Yay, PR #2175 fixed the other issue.

Will adding an explicit reference fix this?

It would make the error go away, but no, I wouldn't say it fixes the actual issue.