[.NET6] msbuild node reuse causes error MSB4044: The "Aapt2Link" task was not given a value for the required parameter "ApplicationName"

[jeromelaban]

Steps to Reproduce

1. Build an application with net6.0-android in a visual studio instance
2. Build an application with `monoandroid11.01 in another visual studio instance

Expected Behavior

No build error.

Actual Behavior

The build randomly fails with:

error MSB4044: The "Aapt2Link" task was not given a value for the required parameter "ApplicationName"

Version Information

.NET 6 preview 2

Log File

[dellis1972]

Thats odd cos our Aapt2* based classes don't have an ApplicationName argument.
I suspect if you want to do this both the .net 6 and the legacy installations will need to be in sync and from the same "release". Since we do change the internals of our MSbuild system quite allot.

@jonathanpeppers does that sound about right?

[jonathanpeppers]

I think what is happening is a newer Xamarin.Android.Build.Tasks.dll is loaded, but running against the old .targets.

It doesn't look like the right assembly is loaded.

[jeromelaban]

The issue can be both ways, net6-android targets with a monoandroid11.0 task, and the other way around depending on which was used first by the build node.

[jonathanpeppers]

So you could probably have 16.10 and 16.9 open at the same time and hit the same issue?

Or is this only a problem when the same VS version is open?

[jeromelaban]

I only use one version of 16.9, but multiple instances, but it looks like msbuild nodes are reused across.

[jonathanpeppers]

This is becoming a bigger issue in .NET 6 Preview 6.

Right now you'd have to install the same build from our release branch:

• https://github.com/xamarin/xamarin-android/tree/release/6.0.1xx-preview6
• https://dl.internalx.com/vsts-devdiv/Xamarin.Android/public/4948326/6.0.1xx-preview6/9a7da6d3e943544abbf67758b50fd5afb21875cc/signed/Xamarin.Android.Sdk-11.4.99.30.vsix

Otherwise you'll run into various errors where the assemblies don't match.

[jonpryor]

The fix for this issue will involve strong-naming Xamarin.Android.Build.Tasks.dll and all dependencies.

See also:

• Bump xamarin-android-tools and StrongName Xamarin.Android.Build.Tasks #6116