Update utilities to launch via AppExecutionAlias rather than directly from the folder to utilize correct AUMID #3022
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
… from the folder to utilize correct AUMID
jaholme
requested review from
andreww-msft,
dabhattimsft,
krschau,
timkur,
EricJohnson327 and
zadesai
dabhattimsft
approved these changes
May 30, 2024
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.
Summary of the pull request
More quality of life improvements for people developing utilities within Dev Home. Now the --UtilityLaunch parameter references an AppExecutionAlias rather than a relative file path. This ensures that apps started this way are running under their own AUMID rather than Dev Home's AUMID.
References and relevant issues
Detailed description of the pull request / Additional comments
Validation steps performed
PR checklist