You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Make Roslyn analyzer for multithreadable tasks available via NuGet package. #13712
Outcome: in scope for the multithreading public preview. Plan agreed; scheduled for the first June sprint.
Plan
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.
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.
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.
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.
Outcome: in scope for the multithreading public preview. Plan agreed; scheduled for the first June sprint.
Plan
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.
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.
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.
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.
Activity
jankratochvilcz commentedon May 14, 2026
Grooming notes (2026-05-13)
Outcome: in scope for the multithreading public preview. Plan agreed; scheduled for the first June sprint.
Plan
WarnAsErrorconsumers) while still giving migrators clear, actionable output.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.
jankratochvilcz commentedon May 14, 2026
Grooming notes (2026-05-13)
Outcome: in scope for the multithreading public preview. Plan agreed; scheduled for the first June sprint.
Plan
WarnAsErrorconsumers) while still giving migrators clear, actionable output.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.