I have a PowerPoint VSTO/C# project that is using the Visual Studio signing capability.
The project was using the Sha256 code signing certificate and was working correctly.
I was able to select the correct signature in the Visual Studio signing tab by clicking on 'Select from Store...'.
Recently I renewed the certificate to DigiCert Global G3 Code Signing ECC SHA384 2021 CA1. Since then, Visual Studio is not able to select my signature.
When I click on 'Select from Store...", I am getting the message:
No certificates available. No certificates meet the application.
I am using Visual Studio 2019 16.11.5.
Is this a limitation of Visual Studio? If yes, is there a possibility to run a post build tool manually to perform the same operation?
I had the similar problem and asked about it there: https://developercommunity.visualstudio.com/t/Visual-studio-doesnt-detect-digicert-co/10135932?port=1025&fsid=d5a2dbf9-137f-411b-aec3-06d687a8d0cf&entry=problem.
Mage tool used by Visual Studio to sing ClickOnce manifests doesn't support ecc public keys. Also I'm not sure if Mage tool supports sha384.
I have a visual studio 2015 project that builds a Outlook Add-In.
I don't want to use click once. I wrote my own installer that properly installs the Add-In. It runs fine except for the warning about it not being signed when loaded into outlook.
My question is I have no idea how to sign the addin. I bought a code signing certificate from godaddy but I don't know what tools to use or what files need to be signed.
Specifics would be greatly appreciated.
Thanks
You can use the SignTool.exe utility. Sign Tool is a command-line tool that digitally signs files, verifies signatures in files, and time-stamps files.
This tool is automatically installed with Visual Studio. To run the tool, use the Developer Command Prompt (or the Visual Studio Command Prompt in Windows 7). For more information, see Developer Command Prompt for Visual Studio.
The following command digitally signs a file by using a certificate stored in a password-protected PFX file.
signtool sign /f MyCert.pfx /p MyPassword MyFile.exe
Finally, you may find the Code Signing – It’s Cheaper And Easier Than You Thought article helpful.
I use visual studio 2010 and I am trying to sign my click once application with given certificate. I have done the following:
Downloaded and Installed crt file to CurrentUser/Trusted Root Certification authorities store.
But when I:
open the Signing tab in my project
press 'Select from store' button there is no certificate that I installed.
Thank You!
What type of certificate did you use?
You need to use the Authenticode PKCS 7 standard which uses X.509 v3 certificates to bind an Authenticode-signed files to the identity of a software publisher.
Please review:
http://msdn.microsoft.com/en-us/windows/hardware/gg487309
While I was trying to Update my Project I was making - I got an error for the first time I've seen:
'An error occurred while signing: SignTool.exe not found.'
I've never seen this before, So I looked up that SignTool.exe is what signs my project for ClickOnce Deployment.
I also read that is it a part of Windows SDK - but when I looked to find where SignTool.exe is - I saw it right there!
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin
I saw no problem, and I've always published my Project all the time - I'm on Version 68. But this is the first time I've seen this - I didn't touch any options that would do this.
Any help?
ClickOnce Publishing Tools are not installed as part of the Typical Installation Options. So you have to install it in advanced mode.
This dialog can be found in Windows 7 by going to Control Panel > Uninstall a program, right-clicking on Microsoft Visual Studio Professional 2015 and selecting Change. A Visual Studio dialog will open up. Select Modify from the set of buttons at the bottom and the above dialog will appear.
Please Click Once application --> Properties --> Signing -> Unchecked the Sign the ClickOnce manifests.
Problem will be solved.
Note: Be aware that this solution removes security from your project. Seek assitance from a more learned colleague before doing so.
SignTool is moved to another location in the last SDK: C:\Program Files (x86)\Windows Kits\8.1\bin\x86
Need to install ClickOnce Publishing Tools during Visual Studio 2015 setup.
You can re-run the Installation from the Programs and Features section; find Visual Studio in the list and click Change.
You can fix this by clicking on installation application of VS. Then click Modify > Mark ClickOnce App and then upgrade your VS. Also i think #Alex Erygin is right. It is a bad solution to Click Once application --> Properties --> Signing -> Uncheck Sign the ClickOnce manifests. This is not a solution. It only circumambulated the problem.
This is a simple fix. Open the project you are getting this error on. Click "Project" at the top. Then click " Properties" ( Will be the name of the opened project) then click "Security" then uncheck "Enable ClickOnce security settings."
That should fix everything.
Click "Project" at the top. Then click " Properties" -> Signing -> Unchecked [Sign the ClickOnce manifests] is now working
Now try to publish the ClickOnce application. If you still find the same issue, please check if you installed the Microsoft .NET Framework 4.5 Developer Preview on the system. The Microsoft .NET Framework 4.5 Developer Preview is a prerelease version of the .NET Framework, and should not be used in production scenarios. It is an in-place update to the .NET Framework 4. You would need to uninstall this prerelease product from ARP.
https://blogs.msdn.microsoft.com/vsnetsetup/2013/11/18/an-error-occurred-while-signing-signtool-exe-not-found/
Lastly you might want to install the customer preview instead of being on the developer preview
None of the answers above talk about disabling ClickOnce. In my situation, I never used ClickOnce for my applications but after I upgraded to VS 2015 it was suddenly enabled and I got the 'SignTool.exe not found' error when I tried to compile.
To disable you go into the properties of your Project (right click) and choose Security | Uncheck Enable ClickOnce security settings.
You can leave the manifest checked in the Signing tab because it has nothing to sign if it's been disabled.
I've confirmed that unchecking the security resolved the compile error on my projects.
I needed Signing hence couldn't un-check as suggested.
Then goto Control Panel -> Programs and Features -> Microsoft Visual Studio 2015 Click Change then the installer will load and you need to click Modify to add ClickOnce Publishing Tools feature.
I did have similar problem. For some reason under
project properties -> Signing -> Sign ClickOnce manifests was enabled.
I unchecked it and the problem went away.
Reinstalling SDK did not help me but installing SDK+.NET 3.5 did from link below:
https://www.microsoft.com/en-us/download/details.aspx?id=3138
Windows 10 users can find signtool.exe in C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64 folder (10.0.18362.0 in my case, or other version).
But first, make sure you've installed Windows 10 SDK
Then, check Windows SDK Signing Tools for Desktop Apps is installed by going to Control Panel > Programs > Programs and Features, choose Windows Software Development Kit - Windows 10.0.18362.1 (in my case, you version may be different), right-click, choose Change, choose options Change then click Next.
I had the same issue/error message just after upgrading Visual Studio Pro 2019 V16.6.0. Solution was to make sure that the signing certificate is valid as mine had expired by a day.
Look in properties and signing to either enter a valid or temporary certificate. To keep the file name the same as before then un-click the security as mentioned above and then delete the key file linked to the programme.
Create a new key file and then add back the security.
Solution Explorer
Your app Right Clik
Propatis
Security
Unchek (Enable ClickOnce Security Settings)
Thats Solve..... __:)
https://i.stack.imgur.com/62nKZ.png See
[enter image description here]
After upgrading build tools in DevOps build agent to visual studio 2019, we started getting the below error for 64-bit build step of a WPF application.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(3975,5): error MSB3482: An error occurred while signing: SignTool.exe was not found at path
I tried all the above answers except the ones to disable signing or signing security and nothing helped.
Disabled the default MSBUILD step
Added a cmd prompt step
The path is
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MsBuild.exe"
Note: Removed amd64 from the path above.
This is still a workaround. I hope Microsoft will fix it in the following release.
For VS 2019 or later (Windows 11)
Option 1 (Recommended) -
ClickOnce Publishing Tools are not installed basic Installation. Therefore you will have to manually check and install.
Go to Visual Studio Installer
Then Click modify
Finally, select Individual components tab, search for ClickOnce Publishing and install
Restart the computer.
Option 2 (Not recommended) -
Click Once application --> Properties --> Signing -> Uncheck Sign the ClickOnce manifests. This is not a solution. A workaround.
Option 3 -
Install Windows 10 SDK. Check Control Panel > Programs > Programs and Features > Windows Software Development Kit
I recently repaired Visual Studio 2005 after getting a publish error.
Now I get the following error. How do I fix it?
Error 2 SignTool reported an error 'Failed to sign bin\Release\TBRHelp.publish\setup.exe. SignTool Error: ISignedCode::Sign returned error: 0x80880253
The signer's certificate is not valid for signing.
SignTool Error: An error occurred while attempting to sign: bin\Release\TBRHelp.publish\setup.exe
I had this exact same problem last week. To solve this problem in Visual Studio 2008, I did the following:
I right clicked on the project and selected Properties.
Then I clicked on tag Signing.
Then I checked the checkbox next to Sign the ClickOnce manifests.
Then I pressed the button Create Test Certificate... and followed the process.
This worked for me, I hope it works for you.
I am using Visual Studio 2008. When clicked on Signer les manifestes ClickOnce, I saw: Date d'expiration on 16/03/2014. Today's is 25/03/2014.
I didn't create a new certificate, but clicked on "A partir du magasin" and followed instructions.
I arrived to a certificate with expiration date at 02/06/2014, from Toshiba... (The name of my computer). I imported it and my date date of the 'expiration change from 16/03/2014 to 02/06/2014.
How can I have an automatic updated certificate date?