Add support for UAP v10.0.10240 #3875
Merged
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
|
can you please take a look at the red build? thanks |
|
It timed out - but I guess you worked that out given that you've closed and re-opened the PR :-) |
|
thanks. this is released in alpha and stable channel |
This was referenced Oct 11, 2021
Closed
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.
This is a fix for #3874.
I think it's right, but I've not used it to build anything which uses the UAP version in question (or any other UAP version for that matter). I have however used it to build a project which uses a Nuget package which declares a dependency for this UAP version, and it prevents it from reporting incorrect errors and warnings (i.e. it fixes the bug described by the issue mentioned above).