Correct MakeAppx.exe usage example #40
Open
Conversation
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.
In the current documentation, it appears such as that "mypackage.msix" is to proceed a value after the "/p" argument, however, that is not the case. If you are to specify the output path and, specifically, the name of the file to be output, it must be part of the "/p" argument value.
The proposed diff tries to address this both in the command example, but goes the length to make a bullet-point dedicated to this alone.
If welcomed, I would be willing to create an interactive PowerShell script which does the procedures specified in the application's README, as I have to do this regardless for a task at my job.