Skip to content

Consider tree-shaking for APIs banned from tasks #14843

Open

Description

@rainersigwald

The MSBuild Task analyzer looks for a set of known-bad APIs in tasks (and helper methods) marked as multithreading-compatible. However as a Roslyn analyzer it sees only the current compilation (DLL), and source code/method calls for referenced DLLs is not easily visible.

It might be interesting to use some of the reference trimming/tree-shaking implementations used for AOT compilation to try to see if there are any paths to banned APIs in the referenced DLLs.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions