Microsoft.Common.CurrentVersion.targets: _SplitProjectReferencesByFileExistence DependsOn AssignProjectConfiguration #11167
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@dsplaisted , @rainersigwald , I've added better screenshots explaining the issue, check it out |
YuliiaKovalova
approved these changes
Mar 17, 2025
|
/backport to vs17.14 |
|
Started backporting to vs17.14: https://github.com/dotnet/msbuild/actions/runs/14040120899 |
This was referenced Jul 28, 2025
This was referenced Aug 4, 2025
This was referenced Aug 24, 2025
Closed
This was referenced Oct 15, 2025
Closed
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When GetCopyToPublishDirectoryItems from Microsoft.NET.Publish.targets is called on its own, the depends tree terminates at _SplitProjectReferencesByFileExistence
_SplitProjectReferencesByFileExistence tries to use @(ProjectReferenceWithConfiguration) , which is empty, because it is emitted by AssignProjectConfiguration, which isn't actually called.
This causes the Publish action to not pick up output of project's ProjectReferences, since they are completely ignored.
Failed call missing projectreferences, AssignProjectConfiguration is not called:
Normal call as part of Publish, AssignProjectConfiguration runs as a dependency of ResolveReferences:
Add the target to the dependson list to ensure that @(ProjectReferenceWithConfiguration) contains something and all projectreferences output is picked up as expected.