Skip to content

Make Roslyn analyzer for multithreadable tasks available via NuGet package. #13712

Closed as duplicate

Description

@AR-May

Review the current analyzer for multithreadable tasks, improve it to production quality, and publish it as a NuGet package.

Scope

  • Finalize analyzer implementation for production readiness
  • Ensure reliability and correctness
  • Package and release via NuGet
  • Update public documentation for task migration to include it

Activity

  1. added this to the .NET 10 milestone on May 7, 2026
  2. added
    Area: TasksIssues impacting the tasks shipped in Microsoft.Build.Tasks.Core.dll.
    on May 7, 2026
  3. jankratochvilcz commented on May 14, 2026

    @jankratochvilcz
    Contributor

    Grooming notes (2026-05-13)

    Outcome: in scope for the multithreading public preview. Plan agreed; scheduled for the first June sprint.

    Plan

    1. Ship the analyzer in the existing framework MSBuild package rather than creating a separate package. No new service ID needed; it rides our normal release cadence.
    2. Default diagnostic severity stays low (Info). The analyzer's per-rule severity is opt-in via the existing multithreadable-task attribute on the task class — applying the attribute lights up the relevant diagnostics at higher severity. This keeps the rollout non-breaking (diagnostics are a breaking change for WarnAsError consumers) while still giving migrators clear, actionable output.
    3. Dogfood internally first. Today the analyzer flags tasks that haven't opted in, which is noisy — fix it to respect the attribute, then turn it on unconditionally inside this repo. Once it's clean against our own code, ship to external consumers.
    4. Update the task-migration documentation to reference the analyzer and the editorconfig knobs for raising severity.

    Why this is preview-blocking

    The public preview isn't only "engine work is done" — it's also "a partner can move their tasks over without painful trial and error." Without the analyzer surfacing the migration rules, early adopters will give us much weaker feedback. The analyzer is also high-leverage for AI-assisted migrations: compilation diagnostics are exactly the signal coding agents pick up and act on.

    Effort

    The remaining work is largely mechanical (plumb the attribute check, package wiring, doc update); a coding agent can carry most of it once the spec above is in the issue body. Quality work on the rules themselves is a separate, ongoing track.

  4. jankratochvilcz commented on May 14, 2026

    @jankratochvilcz
    Contributor

    Grooming notes (2026-05-13)

    Outcome: in scope for the multithreading public preview. Plan agreed; scheduled for the first June sprint.

    Plan

    1. Ship the analyzer in the existing framework MSBuild package rather than creating a separate package. No new service ID needed; it rides our normal release cadence.
    2. Default diagnostic severity stays low (Info). The analyzer's per-rule severity is opt-in via the existing multithreadable-task attribute on the task class — applying the attribute lights up the relevant diagnostics at higher severity. This keeps the rollout non-breaking (diagnostics are a breaking change for WarnAsError consumers) while still giving migrators clear, actionable output.
    3. Dogfood internally first. Today the analyzer flags tasks that haven't opted in, which is noisy — fix it to respect the attribute, then turn it on unconditionally inside this repo. Once it's clean against our own code, ship to external consumers.
    4. Update the task-migration documentation to reference the analyzer and the editorconfig knobs for raising severity.

    Why this is preview-blocking

    The public preview isn't only "engine work is done" — it's also "a partner can move their tasks over without painful trial and error." Without the analyzer surfacing the migration rules, early adopters will give us much weaker feedback. The analyzer is also high-leverage for AI-assisted migrations: compilation diagnostics are exactly the signal coding agents pick up and act on.

    Effort

    The remaining work is largely mechanical (plumb the attribute check, package wiring, doc update); a coding agent can carry most of it once the spec above is in the issue body. Quality work on the rules themselves is a separate, ongoing track.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions