How to add digital signature to the C# code executable

Question

0.00/5 (No votes)

See more:

When using the exe file in other machines, the below error is available. The exe is created using C# code.

This file does not have a valid digital signature that verifies its publisher. You should only run software from publishers you trust.

This should be fixed by adding the certificates. Can you pls help with this?

What I have tried:

I tried adding the Certificate from the solution, but that didn't work

Posted 19-Dec-17 22:56pm

Member 13586221

Updated 20-Dec-17 2:02am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sammuel Miranda · Answer 1 · 2017-12-20T02:02:00

Adding the certificate to the solution should resolve what you need.
If it didn't, then most likely the problem IS THE CERTIFICATE.

The certificates created automaticaly by the Visual Studio don't have a full cascade of CA's (Certificate Authorities) and therefore cannot be used as a base for Full Trust Application Certification.

By using then you may notice that your Applications gain a PublicKeyToken to their references instead of "PublicKeyToken=null"; but that is not what qualifies the software as Full Trust.

To do that you need a certificate fully qualified, with a chain os certification and a CA. That CA needs to be on the trust chain. If you here installing-a-self-signed-certificate-as-a-trusted-root-ca-in-windows-vista you'll see the CA's installed on Windows, and the CA must be there - either because it's a trusted CA native to windows or because you added it manualy (to the client machine).