refreshed CI settings

[moljac]

• bumped several nuget versions
• matching builds for Xamarin.Android

[jonathanpeppers]

Does this also need to update the android workload?

XamarinComponents/azure-pipelines.yml

Lines 80 to 83 in df29e1f

	- pwsh: |
	dotnet workload install android
	displayName: install .NET 6 Android Workload
	condition: ne(variables['System.JobName'], 'linux')

[moljac]

Does this also need to update the android workload?

XamarinComponents/azure-pipelines.yml

Lines 80 to 83 in df29e1f

	- pwsh: |
	dotnet workload install android
	displayName: install .NET 6 Android Workload
	condition: ne(variables['System.JobName'], 'linux')

Not sure. But I think it makes sense to update.

[moljac]

Added snippet for workload installation and update from AX and/or GPS-FB-MLKit

[jonathanpeppers]

Like we did in AndroidX / GPS, can we "spot check" some of the .nupkg files to make sure the file sizes are the same?

[moljac]

Like we did in AndroidX / GPS, can we "spot check" some of the .nupkg files to make sure the file sizes are the same?

this would be quite difficult for XC repo. it builds according to manifest only folder involved in the PR. So if TensorFlow was updated it would build only TensorFlow.

Maybe closing this PR w/o merging?

[jonathanpeppers]

@moljac can you make a small change in Tensorflow to test at least one of them?

[moljac]

@moljac can you make a small change in Tensorflow to test at least one of them?

OK
I will bind the same version as in GPS-FB-MLKit, so that we have one parameter less to take into account.

Should I multitarget net6.0?

We left it here as monoandroid9.0

https://github.com/xamarin/XamarinComponents/blob/main/XPlat/TensorFlow.Lite/source/Xamarin.TensorFlow.Lite.Bindings.XamarinAndroid/Xamarin.TensorFlow.Lite.Bindings.XamarinAndroid.csproj#L12

[jonathanpeppers]

@moljac can you pick one that targets .NET 6? Maybe Xamarin.Android.Glide?

[jonathanpeppers]

This one looks fine now, but does #1398 replace it? It seems like that one also updates the Android workload.

[jpobst]

One thing to keep in mind when changing .yaml files for this repository is that it is set up to always use the YAML from main:
https://github.com/xamarin/XamarinComponents/blob/main/azure-pipelines.yml#L15-L19

Therefore it will never test your PR changes to YAML files. (I do not know why it is set up this way 🤷‍♂️)

This commit breaks the Linux lane with:

Workload ID maui isn't supported on this platform.

As a result we can no longer publish anything out of this repository. We need to figure out if these changes were actually needed, and if so, how can we work around it for Linux.