dotnet/msbuild

Msbuild logs the user specified path for the assembly of a custom task, not the path of the actual assembly that gets loaded

Open

#325 opened on Oct 30, 2015

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (5,062 stars) (1,364 forks)batch import
User Experiencehelp wantedtriaged

Description

On core CLR, this mismatch is caught by the test: TypeLoader_Tests.LoadInsideAssemblyWhenGivenOutsideAssemblyWithSameName

The message gets logged erroneously in here: https://github.com/Microsoft/msbuild/blob/master/src/XMakeBuildEngine/Instance/TaskRegistry.cs#L414

Contributor guide

Tech stack
csharp
Domain
build system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C# basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine TaskRegistry.cs at line 414 in the Microsoft/msbuild repository. The issue indicates that the user specified path is logged instead of the actual loaded assembly path. Investigate the logic in RegisterTaskObject or related methods to understand how the path is determined and propose a fix to log the correct assembly path. Review any existing tests like TypeLoader Tests.LoadInsideAssemblyWhenGivenOutsideAssemblyWithSameName to ensure the fix aligns with expected behavior.