dotnet/msbuild

Consider blocking TaskLoggingHelper use after its task ends

Open

#4,828 opened on Oct 17, 2019

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

Repository metrics

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

Description

see https://github.com/microsoft/msbuild/issues/4792#issuecomment-543336926 and the rest of that thread

If you hold onto a TaskLoggingHelper object (perhaps in a static field) past the lifetime of the Task that created it, it will throw when it is used.

We could instead dispose of it and provide a nicer error at time of use.

Contributor guide

Research direction
Examine the referenced issue thread and implement disposal of TaskLoggingHelper after task ends to provide a cleaner error.
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.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75