Document automating MSIX signing in the Visual Studio / MSBuild build#478
Open
RDMacLachlan wants to merge 1 commit into
Open
Document automating MSIX signing in the Visual Studio / MSBuild build#478RDMacLachlan wants to merge 1 commit into
RDMacLachlan wants to merge 1 commit into
Conversation
The original bug asked for post-build scripting steps to sign an MSIX from Visual Studio using Device Guard Signing (DGSS). DGSS is retired (Microsoft Store for Business/Education retired 2023-03-31) and the DGSS article already redirects to Azure Trusted Signing, so documenting new DGSS scripting is obsolete. Instead, fill the still-open gap with modern guidance. Add an "Automate signing in your Visual Studio build (MSBuild)" section to the end-to-end signing guide covering: - MSBuild signing properties (AppxPackageSigningEnabled, PackageCertificateThumbprint/KeyFile/Password, timestamp URL and algorithm) - Command-line / CI examples using a store certificate or a .pfx file - How to sign automatically inside Visual Studio - Post-build signing with Azure Artifact Signing / Azure Key Vault (build unsigned, then sign the produced .msix) Resolves AB#24788320 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Learn Build status updates of commit 02d8339: ✅ Validation status: passed
For more details, please refer to the build report. |
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.
Resolves the doc gap behind Azure Boards work item AB#24788320.
Background
The original bug (filed 2020) asked for post-build scripting steps to sign an MSIX from Visual Studio using Device Guard Signing (DGSS). DGSS is now retired—Microsoft Store for Business/Education (which DGSS required) were retired on 2023-03-31—and
package/signing-package-device-guard-signing.mdalready carries a retirement banner redirecting to Azure Trusted Signing. Documenting new DGSS scripting would document a dead service.The legitimate, still-open need behind the bug is automating MSIX signing as part of the Visual Studio / MSBuild build, which wasn't covered: the end-to-end guide documented CLI + CI (GitHub Actions, Azure DevOps), and
sign-with-akv-cert.mdcovered the interactive Create App Packages wizard, but neither documented build-time MSBuild signing.Change
Added an "Automate signing in your Visual Studio build (MSBuild)" section to
package/sign-msix-package-guide.md:AppxPackageSigningEnabled,PackageCertificateThumbprint/PackageCertificateKeyFile/PackageCertificatePassword,AppxPackageSigningTimestampServerUrl/AppxPackageSigningTimestampDigestAlgorithm.msbuildexamples using a store certificate or a.pfxfile..msix), linking to the existing sections.ms.dateand addedmsbuild, visual studiokeywords.Property names verified against Microsoft Learn.