Skip to content

Commit

Permalink
Remove erroneous spaces in commands (#2332)
Browse files Browse the repository at this point in the history
  • Loading branch information
riverar authored Apr 2, 2020
1 parent dadbc20 commit f2f61a4
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -119,15 +119,15 @@ After you create your package manifest, build the sparse package by using the [M
The following example demonstrates how to create a sparse package from the command line.

```Console
MakeAppx.exe pack /d <path to directory that contains manifest> /p <output path>\MyPackage.msix /nv
MakeAppx.exe pack /d <path to directory that contains manifest> /p <output path>\MyPackage.msix /nv
```

Before your sparse package can be successfully installed on a target computer, you must sign it with a certificate that is trusted on the target computer. You can create a new self-signed certificate for development purposes and sign your sparse package using [SignTool](https://docs.microsoft.com/windows/msix/package/sign-app-package-using-signtool), which is available in the Windows SDK.

The following example demonstrates how to sign a sparse package from the command line.

```Console
SignTool.exe sign /fd SHA256 /a /f <path to certificate>\MyCertificate.pfx /p <certificate password> <path to sparse package>\MyPackage.msix
SignTool.exe sign /fd SHA256 /a /f <path to certificate>\MyCertificate.pfx /p <certificate password> <path to sparse package>\MyPackage.msix
```

### Add the package identity metadata to your desktop application manifest
Expand Down

0 comments on commit f2f61a4

Please sign in to comment.