Upgrade TFM to net6.0 #357
Conversation
| <!-- using multiple versions of the runtime with the same managed --> | ||
| <!-- executable. --> | ||
| <TargetFramework>netcoreapp3.1</TargetFramework> | ||
| <TargetFramework>net6.0</TargetFramework> |
There was a problem hiding this comment.
I think the comment above still applies, doesn't it?
There was a problem hiding this comment.
@BruceForstall do you see any issues here? I recall having this discussion about .NET Core 3.1 before, but I don't recall whether this allowed us to use PMI on full framework or what the exact reasoning was.
There was a problem hiding this comment.
Yup, netcoreapp3.1 will reach its EOL in about a month (and I think the final servicing has been shipped).
Besides, I doubt we are updating jitutils package to latest releases anymore in dotnet/coreclr repo (where release/3.x code resides).
There was a problem hiding this comment.
We were targeting 3.1 at the request of @jashook . I think it's reasonable at this point to update to 6.0 (EOL announcement/reminder: https://devblogs.microsoft.com/dotnet/net-core-3-1-will-reach-end-of-support-on-december-13-2022/)
BruceForstall
left a comment
BruceForstall
left a comment
There was a problem hiding this comment.
Thanks for the contribution!
This reverts commit 47d70e1.
3 participants
netcoreapp3.1->net6.0COMPlus_env vars withDOTNET_MutateTestRootCommandand updateSystem.CommandLinepackage (as we have in cg2, r2rdump, etc.).cc @jakobbotsch, @BruceForstall