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.

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

Hide ephemeral ProjectRootElements from import enumerations #11474

Merged
merged 2 commits into from
Feb 26, 2025

Conversation

rainersigwald
Copy link
Member

@rainersigwald rainersigwald commented Feb 20, 2025

Work item (Internal use): AB#2381505

Summary

Hides the in-memory-only .props file synthesized to support properties returned from an SDK resolver.

Customer Impact

All C++/CLI builds in Visual Studio are marked as "not up to date", slowing customer builds.

Regression?

Yes. Experience regressed in 17.13 after dotnet/sdk#45364, which revealed this latent MSBuild bug (introduced in #5269 in 2020).

Testing

Automated tests and manual C++/CLI VS scenario testing.

Risk

Low: changes behavior only for elements that use the new flag adopted in #11478.

@rainersigwald rainersigwald requested a review from a team as a code owner February 20, 2025 23:09
@rainersigwald rainersigwald changed the title Introduce IsEphemeral to ProjectRootElement Hide ephemeral ProjectRootElements from import enumerations Feb 25, 2025
Some project systems (C++/CLI) use the list of imports for a project in
the list of fast-up-to-date checks. Because SDK-resolver ephemeral
property-definition files were listed as imports but never existed on
disk, C++/CLI projects were never considered up to date.

Fixes
 - https://developercommunity.visualstudio.com/t/CCLI-projects-are-always-built-since-/10847695
 - https://dev.azure.com/devdiv/DevDiv/_workitems/edit/2381505
@rainersigwald rainersigwald merged commit f1b335d into vs17.13 Feb 26, 2025
10 checks passed
@rainersigwald rainersigwald deleted the exp/mark-ephemeral-and-dont-report branch February 26, 2025 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants