ClickOnce Deployment Code Signing deficiency in Visual Studio Express 2012 - by Rob Sherratt

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 794144 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 7/16/2013 11:01:54 AM
Access Restriction Public


ClickOnce Deployment of  Code Signed applications is deficient in Visual Studio Express 2012. The on-line documentation on ClickOnce deployment in Visual Studio 2012 is also deficient and incorrect.

The mechanisms for "code signing" in Visyal Studio Express 2012 only result in the ClickOnce setup.exe installer being code signed.  The deployed / published user application is NOT code signed during the ClickOnce deployment procedure.

It is necessary  for the developer to download the Microsoft SDK containing "signtool.exe" and add a "BeforePublish" event to the Project File (.vbproj or .csproj) e.g. as follows:

<Target Name="BeforePublish">
    <Exec Command="&quot;C:\Program Files (x86)\Windows Kits\8.0\bin\x86\signtool.exe&quot; sign /f &quot;$(ProjectDir)MyComodoCertificate.pfx&quot; /p MyCertPassword /v &quot;$(ProjectDir)obj\$(ConfigurationName)\$(TargetFileName)&quot;" />
Sign in to post a comment.
Posted by Microsoft on 5/19/2014 at 10:41 AM
We will be fixing this so that the application exe is signed in the next version of VS. For existing projects please use the workarounds described in the blog:
Posted by Microsoft on 7/17/2013 at 8:05 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 7/16/2013 at 11:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(