Track subclasses of MSBuild tasks for telemetry

[Copilot]

Summary

Adds telemetry collection to track user-authored subclasses of Microsoft-owned MSBuild tasks. This data will help inform decisions about making tasks sealed and other API changes. This addresses the requirements outlined in #10855.

Changes

Telemetry Collection

• New telemetry event: build/tasks/msbuild-subclassed tracks subclasses of Microsoft MSBuild tasks
• Data collected: Dictionary mapping Microsoft task names to counts of their subclass usage
  • Example: Microsoft_Build_Utilities_Task: 2 indicates 2 user tasks inherit from Microsoft.Build.Utilities.Task
  • Tracks user-authored (non-Microsoft) tasks regardless of sealed status
  • Property names use underscores instead of dots for telemetry compatibility

Implementation Details

Modified ProjectTelemetry.cs:

• Added TrackTaskSubclassing(Type, bool) method that:
  • Walks the entire inheritance hierarchy to find Microsoft-owned base classes
  • Tracks all user-authored (not Microsoft-owned) subclasses
  • Stores counts in a dictionary mapping base task names to subclass usage
• Telemetry is aggregated per project and logged when the project build completes

Modified AssemblyTaskFactory.cs:

• Added IsMicrosoftAuthoredTask() helper that identifies Microsoft tasks by checking:
  • Assembly name starts with "Microsoft."
  • Assembly is from built-in MSBuild logic location
  • Assembly is a Microsoft package from NuGet cache
• Calls TrackTaskSubclassing() for every task instantiation in CreateTaskInstance()
• Passes whether the task is Microsoft-owned to enable proper filtering

New test file ProjectTelemetry_Tests.cs:

• 6 comprehensive unit tests covering all scenarios
• Tests tracking of both sealed and non-sealed subclasses, Microsoft-owned filtering
• Integration test that verifies telemetry collection during actual builds

Example Output

For a build where users have created 2 custom tasks inheriting from Microsoft.Build.Utilities.Task:

TelemetryEvent: build/tasks/msbuild-subclassed
Properties:
  - Microsoft_Build_Utilities_Task: 2

If users also subclassed other Microsoft tasks:

TelemetryEvent: build/tasks/msbuild-subclassed
Properties:
  - Microsoft_Build_Utilities_Task: 2
  - Microsoft_Build_Tasks_Csc: 1

Performance Considerations

• Minimal overhead: inspects every task but only stores data for subclasses
• Uses a simple dictionary, no complex data structures
• No additional reflection beyond what MSBuild already does
• Telemetry logged once per project, not per task execution

Extensibility

The implementation walks the entire inheritance hierarchy, making it easy to:

• Track subclasses of any Microsoft task at any depth
• Add additional filtering criteria in the future
• Extend to other task characteristics as needed

SDK Integration

Follows the existing telemetry pattern where the SDK's MSBuildLogger aggregates integer properties across builds and sends them to the telemetry backend. See: https://github.com/dotnet/sdk/blob/main/src/Cli/dotnet/Commands/MSBuild/MSBuildLogger.cs

Testing

All tests pass:

• ✅ 6 new ProjectTelemetry tests
• ✅ 84 existing TaskExecutionHost tests
• ✅ 26 existing AssemblyTaskFactory tests
• ✅ Full MSBuild build succeeds
• ✅ Sample projects build successfully

Fixes #10855

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Collect telemetry about MSBuild- and SDK-delivered Tasks that are loaded during the build</issue_title>
<issue_description>### Summary

We want to mark our tasks sealed, but this would be an API breaking change. To justify this change we need data. So we want to collect data about MSBuild, SDK, and generally Microsoft-authored Task usage to drive this decision making.

Background and Motivation

Today tasks shipped by MSBuild and the SDK generally are not sealed. This means that folks consuming our NuGet packages can extend the Tasks and use them in their own code. This presents problems when we want to do things like enlighten our Tasks to support multithreading.

Proposed Feature

When loading Tasks for execution, we should collect metrics on the characteristics of that Task if that Task is shipped by MSBuild.

• if the Task is sealed or not
• if the Task inherits from Microsoft.Build.Utilities.Task (our helper base class)
• (once the multithreaded APIs are in) if the task directly implements IMultiThreadedTask
• (once the multithreaded APIs are in) if the task supports multithreading through the attribute-detection mechanism

In the future we may want expand the set of Task information gathered, and we may want to allow external MSBuild users (like the dotnet SDK) to add Tasks to the set of Tasks to collect this information about, so there should be some extensibility mechanism for both of these.

Alternative Designs

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #12622

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[dotnet-policy-service]

Hello @@copilot, I noticed that you’re changing an .swr file or any file under src/Package/MSBuild.VSSetup.. Please make sure to validate this change by an experimental VS insertion. This is accomplished by pushing to an exp/* branch, which requires write permissions to this repo.

[Copilot]

Pull Request Overview

This PR implements telemetry collection to track user-authored subclasses of Microsoft-owned MSBuild tasks. The purpose is to gather data about task inheritance patterns to inform decisions about making tasks sealed, addressing requirements from issue #10855.

Key changes:

• Adds a new telemetry event build/tasks/msbuild-subclassed that tracks subclass usage counts
• Implements task inheritance hierarchy analysis to identify Microsoft base classes
• Provides comprehensive test coverage for the new telemetry functionality

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/Build/Instance/TaskFactories/AssemblyTaskFactory.cs	Adds Microsoft task detection logic and integrates telemetry tracking into task instantiation
src/Build/BackEnd/Components/Logging/ProjectTelemetry.cs	Implements core telemetry collection with inheritance hierarchy walking and data aggregation
src/Build.UnitTests/BackEnd/ProjectTelemetry_Tests.cs	Provides comprehensive unit tests covering all telemetry scenarios and edge cases