Fast Up-To-Date Check: Project considered up-to-date even its dependency was considered outdated and was rebuilt #9350
Labels
Feature-Up-to-date
Build up-to-date check that avoids shelling out to MSBuild unless necessary.
Triage-Approved
Reviewed and prioritized
Milestone
Visual Studio Version
17.7.6 Pro
Summary
I have solution consist of the following projects (all are sdk-style projects)
ProjectReference
Process.Start
to run some coded out-of-process.Test.zip
It's impossible to reference the Helper.exe project with the
ProjectReference
(as it is executable project).So, the custom msbuild target was implememnted to include the helper.exe into the build project (see
CustomBuildTargetsWin.targets
in the attached solution).In short, such a target do the following:
MSBuild
task to publishhelper.exe
with the desired optionsPublishItemsOutputGroup
target)Content
to theLib
projectHelper
folder (sources and build artifacts) as the inputs (UpToDateCheckInput
) for the Fast Up-to-Date Check (FUTDC)Steps to Reproduce
helper/data/test.txt
- so, we have the changed dependency now.Expected Behavior
All dependendent projects was rebuilded (helper, lib, main) and we see the updated content of the test.txt in the message box when main.exe starts (the last line of the message box).
Actual Behavior
Main project was not rebuilded, the changes of the test.txt was not inlcuded, the old content of the text.txt shown at runtime (the last line of the message box, which is shown on the start)
F5 logs (helper & lib were considered outdated and was rebuilded, but main was considered up-to-date.)
Additional note
If we will use
msbuild
from the command line (so, without the FUTDC), then all the projects will be rebuilded.User Impact
helper
projectLib
The text was updated successfully, but these errors were encountered: