Task assembly may not be reported correctly when multiple tasks of the same name are used

[ladipro]

The prime example is the GenerateResource task which lives in two assemblies: Microsoft.Build.Tasks.Core and Microsoft.Build.Tasks.v3.5. The current approach of keeping track of task assemblies by the bare task name only may lead to an incorrect assembly being reported by the viewer.

The relevant data structure:

MSBuildStructuredLog/src/StructuredLogger/Construction/Construction.cs

Lines 23 to 24 in 7ed4f85

	private readonly Dictionary<string, string> _taskToAssemblyMap =
	new Dictionary<string, string>(StringComparer.OrdinalIgnoreCase);

MSBuild very likely does not provide enough details to fix this without first enhancing the log output in dotnet/msbuild#9290.

[KirillOsenkov]

Yes, I suspect once MSBuild logs a better message this issue will be fixed for free. There are also now messages when an assembly is loaded during task execution, perhaps we can correlate the full path of the assembly with the assembly name using those events.