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.
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
Add test for Binding Projects Incremental Build #8706
Add test for Binding Projects Incremental Build #8706
Changes from 1 commit
dd1f25b
8af4244
10e3e66
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm surprised that this works, given that the
generator
-generated.projitems
file uses XML Namespaces:Wouldn't
compileItems
always be an empty iterator right now?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It worked in my tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why it worked in the tests; if I apply this patch:
then build this branch locally, and do the equivalent of:
Then I see:
but I don't see
# jonp: found //Compile/@Include value
. I also believe that theGeneratedFiles
output property is empty, as it doesn't appear in the diagnostic log.The contents of
gxa-8706.projitems
:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…so I use this stackoverflow answer to add use of an
XmlNamespaceManager
so that the XPath query can. use namespaces, resulting in:and realize, to my horror, that it still doesn't work, because of the
File.Exists()
check: the value offile.Attribute("Include").Value
will be$(MSBuildThisFileDirectory)E.Example.cs
, which will not exist. It will (almost certainly) never exist, because a directory literally named$(MSBuildThisFileDirectory)
will (almost certainly) never exist. (Unless you're bananas and domkdir '$(MSBuildThisFileDirectory)'
, but who would do such a thing?)This in turn means that, as-is,
@(_GeneratedBindingFiles)
will always be empty, which suggests that most of the changes to theGenerateBindings
target are in fact dead code.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…which is a long-winded way of explaining that I think this doesn't work, and is effectively dead (unexecuted) code.
I'm trying to remove it; let's see if anything breaks.