This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 70%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECC%3C/text%3E%3C/svg%3E)
I am trying to sign a VISX file that was created in Visual Studio 2019.
My VISX sign tool version is 16.0.29116.78
My command line is as follows
vsixsigntool.exe sign /v /f "C:\CodeSigning\Tools\my.pfx" /p password /sha1 "33 5d 72 5a 26 6b 7c c1 d5 6c 48 f4 de 46 d2 20 6e c5 53 cd" /t "http://timestamp.digicert.com" C:\Projects\CodeSigning\SampleVSIXPackage\bin\Debug\SampleVSIXPackage.vsix
The output is simply
Server time: Mon Jan 11 10:46:31 2021
VsixSignTool Error: Could not sign package "C:\Projects\CodeSigning\Sample Files to sign\VSIX\SampleVSIXPackage.vsix": Error Code - 80510029.
Error Message: "Unknown error 0x80510029".
Number of files successfully Signed: 0
Number of errors: 1
I have no idea what to do now.
The only reference to the error is https://www.hresult.info/FACILITY_OPC/0x80510029 or https://learn.microsoft.com/en-us/windows/win32/api/msopc/nf-msopc-iopcdigitalsignatureenumerator-getcurrent
Both refer to the same message which is
OPC_E_DS_MISSING_SIGNATURE_TIME_PROPERTY
0x80510029
The SignatureProperty element with the Id attribute value of "idSignatureTime" does not exist or is not correctly constructed.
The VISX was created by the Visual Studio New Project wizard, VisX project and simply compiled.
Any ideas of how to debug this?
The extension.vsixmanifest file contains the following
<PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011">
<Metadata>
<Identity Id="SampleVSIXPackage.cb802016-9d17-488a-a46f-4a7721e39ea0" Version="1.0" Language="en-US" Publisher="Chris" />
<DisplayName>SampleVSIXPackage</DisplayName>
<Description>Empty VSIX Project.</Description>
</Metadata>
<Installation>
<InstallationTarget Id="Microsoft.VisualStudio.Enterprise" Version="[16.0, 17.0)" />
</Installation>
<Dependencies>
<Dependency Id="Microsoft.Framework.NDP" DisplayName="Microsoft .NET Framework" Version="[4.5,)" />
</Dependencies>
<Prerequisites>
<Prerequisite Id="Microsoft.VisualStudio.Component.CoreEditor" Version="[16.0,17.0)" DisplayName="Visual Studio core editor" />
</Prerequisites>
<Assets>
<Asset Type="Microsoft.VisualStudio.VsPackage" Path="SampleVSIXPackage.pkgdef" />
</Assets>
</PackageManifest>
Chris
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 10%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAX%3C/text%3E%3C/svg%3E)
Hi @Chris Crowe , could you tell me that your VSIXSignTool version is 16.0.29116.78 or 16.2.29116.78? Which version of VS2019 are you using?
My VISX sign tool version is 16.0.29116.78
Chris
I installed the VISX package from NuGet
In my packages folder this is the folder that is created
Microsoft.VSSDK.VsixSignTool.16.2.29116.78
Below is the file version properties of the vsixsigntool.exe contained within that folder.
Thank you for your feedback. This issue has been escalated for further investigation.
Let me know if you would like any more information.
7 days later - any updates?
Hi @Chris Crowe , could you tell me where your certificate comes from? Maybe you can refer to the guide to create a signed certificate. If possible, please provide us with your certificate so that we can test it on our side.
Besides, What is the URL http://timestamp.digicert.com in your command?
If you don’t use /sha1 command, does the error still persist?
Hi
The code signing cert is purchased from Thawte/Verisign
Issued by: thawte SHA256 Code Signing CA
I can not give you a copy of the cert for obvious reasons!
Maybe you could purchase a similar one to test your application? Or generate a real one with Microsoft certificate server with the same details?
Signature Algorithm : sha256RSA
valid From: Monday, 8 July, 2019 1:00:00 PM
Valid To : Tuesday, 12 July, 2022 12:59:59 PM
Enhanced Key Usage: Code Signing (1.3.6.1.5.5.7.3.3)
Key Usage: Digital Signature (80)
Chris
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 22%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
Here are several suggestions, please help to try and response the result.
1 please download the latest version"16.2.29116.78" of the VsixSignTool from following link and sign again
https://www.nuget.org/packages/Microsoft.VSSDK.Vsixsigntool
2 please try following command the singe the extension
vsixsigntool.exe sign /v /f "C:\CodeSigning\Tools\my.pfx" /p password C:\Projects\CodeSigning\SampleVSIXPackage\bin\Debug\SampleVSIXPackage.vsix