Microsoft.NET.Publish.targets GetCopyToPublishDirectoryItems depends on AssignProjectConfiguration #45512
Conversation
This file contains 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
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
|
Looks like this is superseded by dotnet/msbuild#11167, is that correct? |
yes, this PR would bring recursiveness that would work against the comment on the target |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 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.
Add the target to the dependson list to ensure all projectreferences are considered