Fix for attempted use of capability API before it was introduced #4620
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.
Issue
The
Windows::Security::Authorization::AppCapabilityAccess::AppCapability
class was not added until the release after the current minimum supported version. This causes a failure when using the COM API on RS5.Change
Check for the existence of
Windows::Security::Authorization::AppCapabilityAccess::AppCapability
, and if it is not present, simply force the caller to be at least medium integrity level.Validation
Successful from both in-proc and OOP cases on an RS5 VM.
Microsoft Reviewers: Open in CodeFlow