Explain when the packageManagement capability is required#482
Open
RDMacLachlan wants to merge 1 commit into
Open
Explain when the packageManagement capability is required#482RDMacLachlan wants to merge 1 commit into
RDMacLachlan wants to merge 1 commit into
Conversation
The PackageManager guidance in non-store-developer-updates.md referenced the packageManagement capability but was self-contradictory about when it's needed: the intro said it "must" be declared yet also that managing your own app works without it, and the manifest section made a blanket "to use the PackageManager APIs you must declare" statement. Replace that with a clear "When is the packageManagement capability required?" section that distinguishes: - Required for silent, non-interactive APIs (AddPackageAsync, AddPackageByAppInstallerFileAsync) and any cross-publisher operation. - Not required when updating your own app interactively via the Request* APIs (RequestAddPackageAsync, RequestAddPackageByAppInstallerFileAsync), which prompt the user for consent. Rework the intro and the manifest section to link to the new explanation and remove the contradiction. Bump ms.date. Resolves AB#25739271 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Learn Build status updates of commit 5dcc290: ✅ Validation status: passed
For more details, please refer to the build report. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Resolves the doc bug reporting that the PackageManager documentation doesn't reference the
packageManagementcapability or explain when the capability is required (AB#25739271).Problem
non-store-developer-updates.mdreferenced the capability but was self-contradictory about when it's needed:packageManagement, yet also that "managing your own app should work without having to declare the capability."PackageManagerAPIs, your app must declare thepackageManagementcapability" — with no "when."That ambiguity is exactly what the bug reports.
Fix
Add a clear "When is the
packageManagementcapability required?" section that distinguishes:Request*APIs (RequestAddPackageAsync, RequestAddPackageByAppInstallerFileAsync), which prompt the user for consent.The intro and manifest section now link to this explanation and no longer contradict each other.
ms.datebumped.Related
Complements #481 (AB#25736442), which added
packageManagement/packageQuerycapability references to other conceptual pages; this PR supplies the authoritative when-required explanation on the primary page.