Skip to content

Make the PSF write-to-install-directory fixup how-to discoverable - #479

Open
Roy (RDMacLachlan) wants to merge 1 commit into
MicrosoftDocs:mainfrom
RDMacLachlan:users/romaclac/docbug-25600703
Open

Make the PSF write-to-install-directory fixup how-to discoverable#479
Roy (RDMacLachlan) wants to merge 1 commit into
MicrosoftDocs:mainfrom
RDMacLachlan:users/romaclac/docbug-25600703

Conversation

@RDMacLachlan

Copy link
Copy Markdown
Collaborator

Resolves the doc gap behind Azure Boards work item AB#25600703.

Background

The bug (filed 2020) asked for a simple, dedicated doc showing how to implement the PSF write-to-install-directory fixup, because "the main PSF doc is overloaded." The bug owner later re-scoped it to "write doc on how to use the re-direction in the PSF."

That dedicated how-to now exists—psf/psf-filesystem-writepermission.md ("How to fix Package Support Framework Filesystem Write Permission errors")—a focused, end-to-end walkthrough of the FileRedirectionFixup with redirectedPaths.packageRelative, listed in the TOC under "How to implement PSF in your package" next to the scripting docs. The core ask is delivered; the remaining gap is discoverability: the overloaded entry-point docs don't route readers to it.

Change

  • package-support-framework.md (Get started): added a [!TIP] in the File Redirection Fixup section linking to the dedicated write-permission how-to for customers who already know their app writes to its install directory.
  • package-support-framework-overview.md: pointed the "writes into the install folder" bullet directly at psf-filesystem-writepermission.md, and the working-directory bullet at psf-current-working-directory.md.
  • psf-filesystem-writepermission.md: added a Related articles section linking back to the PSF overview, get-started, and the other implement-PSF how-tos.
  • Bumped ms.date on the edited files.

No content duplicated—this closes the navigation gap that the bug called out.

The bug asked for a simple, dedicated doc showing how to implement the PSF
"write to install directory" fixup, because the main PSF doc is overloaded.
That dedicated how-to now exists (psf-filesystem-writepermission.md), but the
overloaded entry-point docs don't route readers to it. Close the
discoverability gap instead of duplicating content.

- package-support-framework.md (Get started): add a TIP in the File
  Redirection Fixup section linking to the dedicated write-permission how-to
  for customers who already know their app writes to its install directory.
- package-support-framework-overview.md: point the "writes into the install
  folder" bullet directly at psf-filesystem-writepermission.md, and the
  working-directory bullet at psf-current-working-directory.md.
- psf-filesystem-writepermission.md: add a Related articles section linking
  back to the PSF overview, get-started, and the other implement-PSF how-tos.
- Bump ms.date on the edited files.

Resolves AB#25600703

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 6af65bb:

✅ Validation status: passed

File Status Preview URL Details
msix-src/psf/package-support-framework-overview.md ✅Succeeded
msix-src/psf/package-support-framework.md ✅Succeeded
msix-src/psf/psf-filesystem-writepermission.md ✅Succeeded

For more details, please refer to the build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants