SOLVED

MSIX Packaging Tool: Edit Existing and Signing

%3CLINGO-SUB%20id%3D%22lingo-sub-249748%22%20slang%3D%22en-US%22%3EMSIX%20Packaging%20Tool%3A%20Edit%20Existing%20and%20Signing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-249748%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20open%20a%20signed%20package%20(such%20as%20to%20set%20the%20capabilities)%20when%20the%20updated%20package%20is%20saved%20it%20is%20no%20longer%20signed.%26nbsp%3B%20The%20ability%20to%20specify%20the%20certificate%2Fpassword%20should%20be%20part%20of%20that%20workflow%20also.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-250929%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20Packaging%20Tool%3A%20Edit%20Existing%20and%20Signing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-250929%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20feedback.%20We%20are%20working%20on%20getting%20that%20ability%20added%20in%20for%20our%20next%20release.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

If you open a signed package (such as to set the capabilities) when the updated package is saved it is no longer signed.  The ability to specify the certificate/password should be part of that workflow also.

1 Reply
Best Response confirmed by John Vintzel (Microsoft)
Solution

Thanks for the feedback. We are working on getting that ability added in for our next release.