-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[mac][msbuild] Add MigrateToNewXMTFI to convert TFI to new Xamarin.Mac.NET (opt-in) #5654
Conversation
…c.NET (opt-in) - #5480 - Related: NuGet/NuGet.Client#2572 To allow nuget to target XM Full we need to have a unique TFI (TargetFrameworkIdentifier). However, that's a really scary change to force, so let's opt-in for now. You can set <MigrateToNewXMTFI>true</MigrateToNewXMTFI> in your project or MigrateToNewXMTFI=true msbuild project.csproj to try it out. We can convert the opt-in to an opt-out with sufficient validation \ releases.
Build failure |
Build failure |
Now that we're getting "real" nuget support, we need to stop lying without breaking the world. We're starting by | ||
allowing "opt-in" MigrateToNewXMTFI which will swap your declared TFI to the new hotness. | ||
--> | ||
<PropertyGroup Condition=" '$(MigrateToNewXMTFI)' == 'true' And '$(TargetFrameworkIdentifier)' != 'Xamarin.Mac' And '$(UseXamMacFullFramework)' == 'true' "> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really like abbreviations, so maybe name the variable something like: UseXamarinMacTargetFrameworkIdentifier
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TFI (TargetFrameworkIdentifier) and TFV (TargetFrameworkVersion) are pretty standard msbuild jargon from what i can tell, but I concede the point. Let me think of a better name...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MigrateToNewXMIdentifier
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
UseDesktopFrameworkIdentifier
?
Build failure Test results14 tests failed, 0 tests skipped, 69 tests passed.Failed tests
|
build |
Build failure 🔥 Build failed 🔥 |
build |
Build success |
Also @jstedfast ? |
Just saw the related link to the nuget issue that implements the mapping, should be 👍 once that ships. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be fine, but would require testing on VS to see how the project system works with an updated XM and NuGet.
Right now VS Mac has zero support for building XM Full so a XM Full project w\ this tag would really be unsupported. Not a bad idea to see how it freaks out though. |
Xamarin.Mac.NET
/xamarinmacnet
TFM NuGet/NuGet.Client#2572To allow nuget to target XM Full we need to have a unique TFI (TargetFrameworkIdentifier).
However, that's a really scary change to force, so let's opt-in for now. You can set
in your project or
MigrateToNewXMTFI=true msbuild project.csproj
to try it out.
We can convert the opt-in to an opt-out with sufficient validation \ releases.