Hi dave,
[quoted text, click to view] >the signfile task wants a .cer file. But what we have from
>verisign is a .spc and a .pvk file. How do we sign with those.
The msbuild with Visual Studio 2005 uses the signtool.exe to perform the
operation for the Signfile msbuild task. However the signtool.exe utility
only accepts the Personal Information Exchange (PFX) file format, so you
need to use the PVK2PFX.exe utility to convert SPC and PVK files to PFX
format at first. e.g.:
pvk2pfx -pvk mypvkfile.pvk -pi mypasswd -spc myspcfile.spc -pfx
mypfxfile.pfx -f
Please refer to the following MSDN documentation for its usage:
pvk2pfx Tool
http://msdn2.microsoft.com/en-us/library/aa906332.aspx Once you get the .pfx file, then you can use it in your Signfile task. I
suggest you refer to the following blog article for a sample on how it
works:
A PostBuild Step that Does Something
http://blogs.msdn.com/mwade/archive/2006/10/03/A-PostBuild-Step-that-Does-So mething.aspx
By the way, if you prefer your signcode.exe approach, you can use the
signcode.exe directly in your msbuild project just as the above blog
article suggested--use a custom task which would execute the following
command:
<Exec Command='signcode -spc WindwardKeys.spc ... ... ' />
Thanks!
Best regards,
Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx. ==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
