MessagePack.Generator.csproj target to net7.0 - #1542
#1542MessagePack.Generator.csproj target to net7.0#1542neuecc wants to merge 2 commits intomasterMessagePack-CSharp/MessagePack-CSharp:masterfrom mpc-update-net7MessagePack-CSharp/MessagePack-CSharp:mpc-update-net7Copy head branch name to clipboard
Conversation
AArnott
left a comment
There was a problem hiding this comment.
I am surprised this change is necessary since we already have <RollForward>Major</RollForward> in this project file, but I have no objection to this change if it fixes the problem.
If you're noticing the Azure Pipelines status failure, it isn't because of this PR. It's because I was too eager to delete my own unity agent once I switched the develop branch to use GitHub Actions. I'll try to adapt that change to the master branch as well. |
|
See #1543 for a fix for the PR build. |
|
Oh, I see now. The master branch still uses the .NET 6 SDK so you can't target .NET 7. Will that suffice? I did ship a beta from the develop branch a few days ago (https://www.nuget.org/packages/MessagePack/2.5.64-alpha) so you can even try it out. |
|
This pull request is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
If only install dotnet sdk 7,0(does not install sdk 6.0)
mpc fail to get metadata so can't execute it.
using net7.0 success.
@AArnott require to change global.json and CI?