Skip to content

Analyzers for MSBuild task authors #15027

Open
2 of 3 issues completed
Open

Description

@AR-May

It is not easy for Task authors cannot to tell by reading their own code whether it is safe to run on a thread. Analyzers find these problems at build time instead: process-wide state, unsafe path handling, and APIs that are never safe inside a task. Without them, migrating the task ecosystem to multithreaded mode depends on manual review.

This epic covers all analyzer work, from shipping the first release to the enhancements that follow.

Steps

  • #14078 Ship the v1 analyzers to task authors [0.5 dev weeks] [Milestone: September 2026]
  • #14772 Enhance the analyzers and fix the bugs after shipping [3 dev weeks] [Milestone: February 2027]

Stakeholders

Task authors in dotnet/sdk, dotnet/nuget, dotnet/roslyn, dotnet/arcade and the VMR, plus task authors referencing latest Microsoft.Build.Framework.

Definition of done

Task authors get the analyzers automatically with MSBuild, and the analyzers catch the unsafe patterns that task migration has actually hit.

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions