Skip to content

Changed "Beginning in 2015" #1703

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 17, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/extensibility/signing-vsix-packages.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Extension assemblies do not need to be signed before they can run in Visual Stud
If you want to secure your extension and make sure it hasn't been tampered with, you can add a digital signature to a VSIX package. When a VSIX is signed, the VSIX installer will display a message indicating that it is signed, plus more information about the signature itself. If the contents of the VSIX have been modified, and the VSIX has not been signed again, the VSIX installer will show that the signature is not valid. The installation is not stopped, but the user is warned.

> [!IMPORTANT]
> Beginning in 2015, VSIX packages signed using anything other than SHA256 encryption will be identified as having an invalid signature. VSIX installation is not blocked but the user will be warned.
> Beginning with Visual Studio 2015, VSIX packages signed using anything other than SHA256 encryption will be identified as having an invalid signature. VSIX installation is not blocked but the user will be warned.

## Signing a VSIX with VSIXSignTool
There is a SHA256 encryption signing tool available from [VisualStudioExtensibility](http://www.nuget.org/profiles/VisualStudioExtensibility) on nuget.org at [VsixSignTool](http://www.nuget.org/packages/Microsoft.VSSDK.Vsixsigntool).
Expand All @@ -44,4 +44,4 @@ Extension assemblies do not need to be signed before they can run in Visual Stud
VSIXSignTool.exe sign /f \<certfile> /p \<password> \<VSIXfile>

## See Also
[Shipping Visual Studio Extensions](../extensibility/shipping-visual-studio-extensions.md)
[Shipping Visual Studio Extensions](../extensibility/shipping-visual-studio-extensions.md)