Update AppServices Microsoft.Windows.SDK.Contracts package to 10.0.22621.2428 #522
+1
−1
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.
@dpaulino was seeing an issue trying to use the AppServices library from a UWP app:
I'm not too sure what happened, but seemed familiar to issues I had faced updating to the latest WASDK when the contracts and stuff weren't also updated alongside. Wonder if some of the updates to our build/tooling have caused a requirement shift here?
Anyway, I tried forcing an update to the project for the
Microsoft.Windows.SDK.Contracts
package to the latest stable10.0.22621.2428
and that seemed to resolve the build issue.Figure updating that in the package here should hopefully resolve the issue without having to declare it in the app?
@dpaulino once this builds, you should be able to try the PR feed one and see if it resolves the issue directly.