First, the strong-signature
This is the concept .net in order to ensure the assembly itself is not tampered with, this assembly is to ensure that you develop, while strongly named the different programs can specify a different set of versions of the program, without affecting other applications. To be a strong sign your assembly, without the use of code-signing digital certificate purchased, sn .NET tools provided by snk files can be generated, as long as you keep this file, you can ensure that your signature assembly.
Method 1: Create a strong name in the SDK assemblies (Sn.exe), you can generate a key pair. Figure 9-4 we use the command generates a new key pair and save it to a local file test.snk in.
Use the compiler to perform CSC, keyfile signature: f: test.snk Program.cs
Method 2: Use VS project property page
Second, the installation program digital signature
When the window system is installed, install the execution of the program, the system first stop, and prompts the user whether or not to run this time, and it will prompt the application of the issuer. If a no application of digital signatures, this time the issuer on the "unknown", after the signature, you can inform the user of this application is provided to you for. This is to ensure that the digital signature is issued by your application, a third party has not been changed.