Hi @VytautasSlivinskas-0957 ,
Thank you for sharing detailed information with me.
It seems that this issue is related to CLR, actually, Visual Studio 2010 is end of support and .NET Framework 3.5 is an old version of .NET Framework, so there are fewer related official documents which mentioned if VS 2010, .NET Framework 3.5, and VSTO project support SHA256.
But, from the error message, I think .NET Framework 3.5 may not support SHA256, so I may suggest you update VS to a higher version, and use .NET Framework 4.0+(If possible).
Best Regards,
Tianyu
- If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Yes I'm developing VSTO project in Visual Studio 2010 with .NET Framework 3.5
In .vsto file I Found this line: <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
I have bought SHA256 certificate for my Excel COM Add-in. I choose my certificate in Project Properties -> Signing -> Select From File -> entering password -> I can see all info of certificate but if I try to BUILD project I receive error: I will put it in 2 comments cause I see we have here 1000 characters limit.
System.Deployment.Application.InvalidDeploymentException: Exception reading manifest from file:///C:/Users/MyProject/bin/Release/MyProject.vsto: the manifest may not be valid or the file could not be opened. ---> System.Deployment.Application.InvalidDeploymentException: Manifest XML signature is not valid. ---> System.Security.Cryptography.CryptographicException: SignatureDescription could not be created for the signature algorithm supplied.
at System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo(AsymmetricAlgorithm key)
at System.Security.Cryptography.Xml.SignedXml.CheckSignatureReturningKey(AsymmetricAlgorithm& signingKey)
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
--- End of inner exception stack trace ---
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- End of inner exception stack trace ---
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.GetManifests(TimeSpan timeout)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
Sign in to comment