[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.
I don't really like abbreviations, so maybe name the variable something like: UseXamarinMacTargetFrameworkIdentifier?
There was a problem hiding this comment.
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.
MigrateToNewXMIdentifier ?
There was a problem hiding this comment.
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. |
kzu
left a comment
There was a problem hiding this comment.
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/xamarinmacnetTFM 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.csprojto try it out.
We can convert the opt-in to an opt-out with sufficient validation \ releases.