Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fast Up To Date Check fails for files linked from a neighbor project #9124

Closed
gleblebedev opened this issue Jun 26, 2023 · 3 comments · Fixed by #9130 · May be fixed by #9133
Closed

Fast Up To Date Check fails for files linked from a neighbor project #9124

gleblebedev opened this issue Jun 26, 2023 · 3 comments · Fixed by #9130 · May be fixed by #9133
Assignees
@drewnoakes
Labels
Bug This is a functional issue in already written code. Feature-Up-to-date Build up-to-date check that avoids shelling out to MSBuild unless necessary. Regression Regressions from a previous (typically public) build or release. Resolution-Fixed The bug has been fixed, refer to the milestone to see in which release it was fixed.
Milestone
17.7

Comments

@gleblebedev
Copy link

gleblebedev commented Jun 26, 2023 •
edited

Visual Studio Version

17.6.3

Summary

Build system ignores changes in files when they referenced from multiple projects. Setting DisableFastUpToDateCheck to true mitigates the issue.

Steps to Reproduce

  1. Download attached sample project.
  2. Run both projects. Observe output value.
  3. Change text file in the first project. Run both projects.

Expected Behavior

The output should change too

Actual Behavior

The output prints original text file content

User Impact

Users have to clean or rebuild the project every time a content file changed.

https://cdn.discordapp.com/attachments/732310858776182866/1122298127647506432/bug.mp4
MSBuildBufRepro.zip
@drewnoakes drewnoakes added the Feature-Up-to-date Build up-to-date check that avoids shelling out to MSBuild unless necessary. label Jun 27, 2023
@drewnoakes
Copy link
Member

Thanks for the bug report.

VS has a special-case handling when launching a debugger (e.g. via F5), which is triggering a bug in the FUTDC. I will get this fixed.

A workaround for now is to build before launching (you don't have to _re_build, just a regular build will do the trick). The issue only occurs when the build happens as part of launching the debugger.

@drewnoakes drewnoakes self-assigned this Jun 27, 2023
@drewnoakes drewnoakes added Bug This is a functional issue in already written code. Regression Regressions from a previous (typically public) build or release. labels Jun 27, 2023
@drewnoakes drewnoakes added this to the 17.7 milestone Jun 27, 2023
@drewnoakes
Copy link
Member

I believe this is a duplicate of the feedback ticket https://developercommunity.visualstudio.com/t/Copy-if-newer---Issue-when-only-non-sour/10308822. We'll keep this GitHub issue open too to track the fix.

@drewnoakes drewnoakes mentioned this issue Jun 28, 2023
Merged
@ghost ghost added the Resolution-Fixed The bug has been fixed, refer to the milestone to see in which release it was fixed. label Jun 28, 2023
@drewnoakes
Copy link
Member

Fixed in #9130 which should make the next 17.7 preview.

@drewnoakes drewnoakes mentioned this issue Jun 29, 2023
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@drewnoakes drewnoakes

Labels
Bug This is a functional issue in already written code. Feature-Up-to-date Build up-to-date check that avoids shelling out to MSBuild unless necessary. Regression Regressions from a previous (typically public) build or release. Resolution-Fixed The bug has been fixed, refer to the milestone to see in which release it was fixed.
Projects
None yet
Milestone
17.7
2 participants
@drewnoakes @gleblebedev