Build Optimization Analyzer for long build times

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

Our solution is fairly complex, and in building it we often find Visual Studio 2019 just seems to hit one csproj at random that it slows to a crawl to build.
Possibly we're doing something sub-optimal, or have a dodgy build.props stage or vs-extension or code-analysis NuGet installed. A verbose-level build output might not surface certain problems, and certain others it may surface but rely on human-inference to connect the dots (e.g. too many 'copy-always' instead of 'preserve-newest') ... if they'd even question it (does component C really need all the localized resources of component A copied to it bin dir too?).

A "build optimization analyzer" feature might be handy to tell what's taking so long and what to do about it.
A related capability might detect why running a unit-test launched a build though a build had just finished. If this is our mistake, or from an optional extension, we'd save a lot of time avoiding the cause.

This could also be used by VS telemetry itself: Roslyn reporting there's 10_000 lines of C# in the component, yet it takes 5 min to build on a 12core box, Msft would probably like to have more visibility into such occurrences in the wild, not just rare, vague, and anecdotal feedback.

---

Original Comments

Feedback Bot on 7/7/2021, 07:27 PM:

Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. We'll provide an update once the issue has been triaged by the product team.

[Evangelink]

As far as I understand the suggested analyzer is not really a "source code" analyzer so I don't think there will be anything done in this repo.

cc @mavasani

[mavasani]

@Evangelink Agreed.