![]() If you specify in the file that your VSIX package only targets Visual Studio 2012 (11.0) and 2013 (12.0): Īnd you sign the VSIX file with with the /fd sha1 option to use the SHA1 algorithm (do not confuse with the /sha1 option, which is used to select the correct certificate): vsixsigntool.exe sign /f CodeSigningCertificate.pfx /sha1 "" /p MyPassword /fd sha1 MyVSIXProject.vsix In the samples that follow, I will assume that you have the vsixsigntool.exe file and a code signing certificate named CodeSigningCertificate.pfx in the same bin\debug folder that contains a vsix file named MyVSIXProject.vsix. You need to use the vsixsigntool.exe that you can get from NuGet:Īnd the official documentation to sign VSIX packages is here: To code sign a vsix file, you can’t use the regular signtool.exe tool of the Windows SDK. In that article I didn’t explain how to code sign such VSIX file to work with multiple Visual Studio versions but this week I have got a (personal) code signing certificate.įirst things first, if you don’t code sign your VSIX file, the VSIX installer shows that the digital signature is none: You know that I am such a big fan of targeting multiple Visual Studio versions with the same VSIX file that I wrote an article for MSDN Magazine explaining the approach to target from Visual Studio 2012 to Visual Studio 2017.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |