Repository navigation
Description
Summary
This issue tracks the initial shipping work for the TaskAnalyzer / task-authoring analyzers as a sub-issue of #14078. It should remain focused on the first safe public release and should not be used as a catch-all for follow-up analyzer-quality work.
The default behavior work is already complete and has already been addressed by earlier merged PRs. This issue begins at the packaging and release-readiness stage for the initial shipping milestone.
Related epic
- Ship the MSBuild task-authoring analyzers #14078: Ship the MSBuild task-authoring analyzers
Shipping sequence
This issue should cover the shipping work in the following order:
-
Package the analyzer into
Microsoft.Build.Framework- Put the analyzer under
analyzers/dotnet/cs - Ensure the framework package installs and activates the analyzer without a direct TaskAnalyzer package reference
- Set the shipping configuration and remove any non-shipping packaging settings
- Put the analyzer under
-
Add package-consumption validation tests
- Verify regular task projects remain warning-free by default
- Verify MT task projects receive the expected analyzer diagnostics
- Verify migration mode and opt-out behavior
- Verify warnings-as-errors and suppression behavior
-
Complete docs and release metadata
- Update README and public guidance to match the shipped behavior
- Document the default MT-only behavior, migration mode, configuration, suppression, and warnings-as-errors semantics
- Ensure package notes and release metadata match the actual product behavior
-
Final shipping signoff and publish
- Complete the final validation pass against consumer scenarios
- Publish the first safe baseline package
- Perform the final release signoff and communication required for the initial public rollout
Scope
- Package the analyzer through
Microsoft.Build.Framework - Ensure analyzer discovery works from the framework package without a direct TaskAnalyzer reference
- Preserve the safe default behavior for non-MT tasks; no new default warnings or errors
- Validate the approved default MT-only behavior and the explicit migration mode
- Add package-consumption tests for the shipping contract
- Confirm that docs and release metadata reflect the actual shipped behavior
- Complete final shipping signoff and publication readiness
Definition of done
- The analyzer ships through
Microsoft.Build.Frameworkas part of the initial public release - Regular, non-MT tasks receive no new default warnings or errors
- MT tasks receive the expected diagnostics under the approved default scope
- Migration mode is documented and validated for regular tasks
- The generated package contains the analyzer under the correct
analyzers/dotnet/cspath - Package-consumption tests pass and cover the approved shipping contract
- The README and release metadata reflect the actual shipped behavior
- The release is approved and ready to ship as part of Ship the MSBuild task-authoring analyzers #14078
Notes
This issue is intentionally limited to the initial shipping work for the analyzers. Follow-up improvements such as false-positive reduction, transitive-analysis refinements, and other analyzer-quality work belong in separate issues and should not block the first safe public shipping milestone.
External communication should be minimal and targeted: release notes plus internal notification to affected consumer teams (SDK/VMR/Arcade/task authors) explaining that this is the initial safe baseline and that follow-up improvements continue after ship.
Activity
[-]Shipping readiness for task-authoring analyzer release[/-][+]Ship TaskAnalyzer through Microsoft.Build.Framework with a safe MT-only default[/+][-]Ship TaskAnalyzer through Microsoft.Build.Framework with a safe MT-only default[/-][+]Ship the MSBuild task-authoring analyzers through Microsoft.Build.Framework[/+]Ship TaskAnalyzer as a separate package with safe defaults (dotnet#15045