12

Visual studio offers me the ability to Sign my assembly / Manifest through the public wizard. However, in order to utilize this functionality, it seems as though I am required to create an installer for my program. I do not want to have to install my executable (anywhere). I would much rather be able to build a single executable and copy this executable into multiple directories (All with a certificate).

I'm assuming there must be some workaround for this, and I would love to hear any suggestions.

RBT
  • 24,161
  • 21
  • 159
  • 240
  • Important to know in this context - [Strong naming in Visual Studio vs. Authenticode signing with a well-known CA certificate](https://stackoverflow.com/q/4469646/465053) – RBT Aug 31 '21 at 07:24

1 Answers1

8
  1. Open your project.
  2. Under Solution Explorer, double click on Properties.
  3. Click Signing.
  4. Click Sign the assembly.
  5. Click the dropdown box, and then select <New...>.
  6. Enter in your desired information and click OK.
Nahydrin
  • 13,197
  • 12
  • 59
  • 101
  • This is what I have been doing? Was I mistaken - I could have sworn this required me to make an installer –  Jul 18 '11 at 18:42
  • No this does not require an installer. When you build the application, it is automatically signed. – Nahydrin Jul 18 '11 at 18:43
  • Is there some simple way to verify the certificate is present? Thank you –  Jul 18 '11 at 18:50
  • 1
    You can use "sn -vf myassembly.dll" (with your assembly name) at a command prompt. That tells you if the assembly is "strongly named", which is what the signing tab on project properties controls. If you meant signing with an Authenticode certificate, that's something else entirely. – Jim Flood Jul 19 '11 at 22:31
  • Thanks for the concise instructions. I knew there must be an easier way than doing this from the command line! – Preston McCormick Apr 26 '12 at 21:28
  • 3
    I signed like this, still when i send the exe to someone else it is flagged as virus. what am i doing wrong – anandhu Sep 11 '20 at 11:38