You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The prime example is the
GenerateResource
task which lives in two assemblies:Microsoft.Build.Tasks.Core
andMicrosoft.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
MSBuild very likely does not provide enough details to fix this without first enhancing the log output in dotnet/msbuild#9290.
The text was updated successfully, but these errors were encountered: