I have a certificate issued by a CA on our intranet (it's a V3 sha1 pfx file).
When I use this in the signing part of my clickonce (vsto addin) project, I get the error:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v9.0\OfficeTools\Microsoft.VisualStudio.Tools.Office.Office2007.targets(250,9): error MSB3482: An error occurred while signing: Invalid provider type specified.
Does anyone know what's going on here?
Thanks!
Did they give you the right kind of certificate, one to sign code with? From what I understand, those are different than certificates used for SSL on a server. Maybe they didn't create it correctly; what did they specify as the provider type?
If you go into the cert manager (type Certmgr.msc in the run box) and look at your certificate, is the provider type listed?
I checked my certificate manager, and I don't see provider type on any of my certificates purchased from a CA or any that I've created myself using MakeCert of Visual Studio, so I have nothing to compare it with.
RobinDotNet
visit my ClickOnce blog
It seems that the V3 certificate issued by out Windows 2008 CA was too advanced for my humble .Net 2.0 VS2008 installation... the solution for me was to get out CA to issue a Windows 2003 compatible version of the certificate, and hey-presto, I can use it to sign my lovely cruddy code!