Skip to content

Target .NET Core 3.1 and 5.0 SDKs in mpc tool#1124

Merged
AArnott merged 3 commits intoMessagePack-CSharp:developfrom
pCYSl5EDgo:Multi
Nov 19, 2020
Merged

Target .NET Core 3.1 and 5.0 SDKs in mpc tool#1124
AArnott merged 3 commits intoMessagePack-CSharp:developfrom
pCYSl5EDgo:Multi

Conversation

@pCYSl5EDgo
Copy link
Copy Markdown
Contributor

This is for the issue #1102 .

Copy link
Copy Markdown
Collaborator

@AArnott AArnott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just tested packing the mpc tool and installing into a project that uses the .NET Core 3.1 SDK, and it failed in a similar way to how mpc fails on the .NET 5 SDK today without changes. We need it to work in both worlds or we alienate a bunch of users.

Repro project:
mpc.zip

Copy link
Copy Markdown
Collaborator

@AArnott AArnott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, never mind. I failed to run dotnet restore after changing the target framework in the repro. It appears to work great

@AArnott AArnott added this to the v2.3 milestone Nov 19, 2020
@AArnott AArnott assigned AArnott and unassigned AArnott Nov 19, 2020
@AArnott AArnott changed the title MPC:Multi Target Frameworks Target .NET Core 3.1 and 5.0 SDKs in mpc tool Nov 19, 2020
@AArnott AArnott merged commit e03abbb into MessagePack-CSharp:develop Nov 19, 2020
@pCYSl5EDgo pCYSl5EDgo deleted the Multi branch November 19, 2020 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants