-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Conversation
ValueTuple is only inbox after a certain version on mono. Should the change be conditional on the version of mono? |
This doesn't apply for Mono, that behaves as desktop so its stuck getting the desktop binary. Xamarin doesn't version their TFMs in a way that lets you target the framework API so those frameworks are stuck getting the behavior of the latest SDKs. |
Marking this as NO-MERGE since we need to wait for 1.1.0 to exit lock down and need to add the build-tools update. This is somewhat dependent on #16119 which does the boiler-plate work to version the ValueTuple package for servicing. |
Now that #16119 is not going in we need to bring over the versioning changes to this PR. |
Brought those commits over. I expect this to fail during package validation until we can get dotnet/buildtools#1348 |
283c949
to
ce0b320
Compare
This is ready to go, @jcouv and @marek-safar can you guys please try |
I've run the tests from I'm now trying to do the same with the .Net Standard portion of the package. But I'm having trouble getting XUnit to work on .Net Standard 1.0 or 1.1. I'll keep you posted. |
@marek-safar / @mhutch / @akoeplinger can one of you ack this and do whatever testing you need to make sure it satisfies your ask? Given this fix is specifically for Xamarin TFMs I want to make sure it gets tested there. |
Thanks for the tips @ericstj |
@marek-safar / @mhutch / @akoeplinger Can you validate the change with mono? Thanks in advance. |
@ericstj, can this be merged now? |
Let me double check with ship-room on that. We had early approval before the buildtools changes went in I just want an ACK that we're OK to merge. |
We have the green light. Merging |
Require buildtools update to build w/o validation errors.
dotnet/buildtools#1348
Fixes: #14235
/cc @jcouv @marek-safar @weshaggard