dotnet/msbuild

Infer AssemblyFile if TaskFactory is used

Open

#1,419 opened on Dec 1, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (1,364 forks)batch import
Area: Enginehelp wantedtriaged

Repository metrics

Stars
 (5,062 stars)
PR merge metrics
 (Avg merge 11d 7h) (125 merged PRs in 30d)

Description

It's no small annoyance to have to know the full file name as well as versioning scheme of the tasks assembly, which has been a moving target in almost every version of MSBuild.

To the point that I ended up creating a nuget package that gives me a $(CodeTaskAssembly) that works reliablely across all MSBuild versions.

So, how about just having MSBuild automatically fill the AssemblyFile for me whenever I use a TaskFactory="CodeTaskFactory" attribute in a UsingTask? Or maybe even more concise yet, just give me a separate element name for it, like UsingCodeTask or something and do away with the attributes altogether :)

May be a superset of what's asked for in #897?

Contributor guide

Research direction
Examine the TaskFactory and UsingTask elements in MSBuild source code to understand how AssemblyFile is resolved. Propose a modification to automatically infer AssemblyFile when TaskFactory is 'CodeTaskFactory'.
Tech stack
csharp
Domain
build system
Issue type
Feature
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
MSBuildC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60