2

I have a XAML browser application created in Visual Studio that I am trying to deploy to a client. (Using Visual Studio 2015 Community.)

In attempting to sign my ClickOnce assembly using a commercial certificate (SHA256 algorithm), Visual Studio is giving the following error message:

C:\Program Files\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(3616,5): error MSB3482: An error occurred while signing: Failed to sign bin\Debug\app.publish\ [assembly name] .exe. SignTool Error: Invalid option: /fd


Previously we were using a self-issued test certificate which utilized SHA1 with the following settings:

enter image description here


But when tried with a self-issued SHA256 test certificate (or using the commercial certificate which is also SHA256) with the following settings we receive the aforementioned error.

enter image description here

Any ideas on how to get Visual Studio to use these SHA256 certificates?

Lemonseed
  • 1,644
  • 1
  • 15
  • 29
  • Check http://stackoverflow.com/questions/21844014/signtool-not-signing-clickonce-app-using-sha256-only-uses-sha1 – Frode May 13 '16 at 08:43
  • Do you have familiarity with this issue? That page has output that the sign tool is successfully running. I am receiving an error. – Lemonseed May 13 '16 at 08:48

1 Answers1

1

Are you sure you are using newest version of SignTool? The easiest way to perform the update to the newest version is to go to the Program and Features, select Visual Studio 2015 Community, click Change in the popup window select Modify. Ensure you selected the Selecting ClickOnce Publishing Tools option. After installation retry your operation. Selecting ClickOnce publishing tools enter image description here

ΦXocę 웃 Пepeúpa ツ
  • 47,427
  • 17
  • 69
  • 97
Endnadus
  • 11
  • 1
  • We ended up having DigiCert re-issue the certificate as SHA1. Visual Studio absolutely would not play nice with SHA256. The installation was fresh at the time (May 2016) with the latest version of Visual Studio 2015 Community at that time. We did not try again after Update 2 or Update 3 came out; perhaps someone could attest as whether or not this was a bug and/or if it was fixed? – Lemonseed Jun 28 '16 at 22:34