dotnet / dotnet/project-system

Improve FUTDC handling of copy items under UseCommonOutputDirectory

Open
#9,143 2 comments 1 reaction 1 assignee Claimed by @drewnoakes View on GitHub
Feature-Up-to-date Performance-Scenario-Build Tenet-Performance Triage-Investigate
Dominant language
C#
Stars
1k
Forks
415
PR merge metrics
No merged PRs in 30d

Description

The [docs](https://learn.microsoft.com/en-us/visualstudio/ide/how-to-change-the-build-output-directory?view=vs-2022#to-place-all-solution-outputs-in-a-common-directory) describe `UseCommonOutputDirectory` as:

> Setting `UseCommonOutputDirectory` to `true` tells Visual Studio and its underlying build engine (MSBuild) that you're putting multiple project outputs in the same folder, and so MSBuild omits the copying step that normally happens when projects depend on other projects.

The FUTDC tracks copy items, but doesn't take into account the value of `UseCommonOutputDirectory`.

We should understand how this property impacts the selection of items we need to track, and change the logic accordingly.

The customer impact here is that we may either build more often than we need to, or may copy more files into the output than needed (if using Build Acceleration).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.