Skip to main content

How to Sign a C# .Net WPF Application

 To sign a C# WPF .NET 6 application, you can follow these steps:

  1. Generate a strong name key pair:

    • Open the Developer Command Prompt for Visual Studio (search for it in the Start menu).
    • Navigate to the project directory using the cd command.
    • Run the following command to generate a strong name key pair:
      sn -k keypair.snk
  2. Configure your project to use the strong name key pair:

    • In Visual Studio (prior to 2022), open your WPF project.
    • Right-click on the project in the Solution Explorer and select "Properties."
    • In the project properties, go to the "Signing" tab.
    • Check the "Sign the assembly" checkbox.
    • Click the "..." button next to the "Choose a strong name key file" field and browse to select the keypair.snk file you generated in the previous step.
    • Click "OK" to save the changes.

  3. Configure the project for ClickOnce deployment (optional but recommended for distributing your application):

    • In the project properties, go to the "Publish" tab.
    • Click the "Publish Now" button to create a publish profile.
    • In the publish profile settings, you can configure the deployment options according to your needs.
    • Click "Publish" to generate the ClickOnce deployment files.

  4. Build and sign the application:

    • Build your application by pressing Ctrl+Shift+B or selecting "Build" > "Build Solution" from the Visual Studio menu.
    • The build process should automatically sign the assembly using the strong name key pair you configured.

  5. Verify the assembly signing:

    • After the build completes successfully, you can verify that the assembly is signed by opening the generated executable file using a tool like ILDASM (IL Disassembler) or JetBrains dotPeek.
    • Look for the .publickey directive in the disassembled code to confirm that the assembly is signed.

By following these steps, you should be able to sign your C# WPF .NET 6 application using a strong name key pair. Remember that strong name signing provides a level of identity verification but does not provide protection against tampering. If you require additional security or want to ensure the integrity of your application, consider using code signing certificates.

For Visual Studio 2022, the following steps may apply

  1. Configure your project to use the strong name key pair:

    • In Visual Studio 2022, open your WPF project.
    • Right-click on the project in the Solution Explorer and select "Properties."
    • In the project properties, navigate to the "Build" section.
    • Check the "Sign the assembly" checkbox.
    • Click the "..." button next to the "Choose a strong name key file" field and browse to select the keypair.snk file you generated earlier.
    • Click "OK" to save the changes.
  2. Build and sign the application:

    • Build your application by pressing Ctrl+Shift+B or selecting "Build" > "Build Solution" from the Visual Studio menu.
    • The build process should automatically sign the assembly using the strong name key pair you configured.


Comments

Popular posts from this blog

Fixing a https Cert in Windows

 I renewed a https cert today in Windows and had problems with the new Cert sticking in Windows It would add fine, without error, but would disappear when the IIS Server Certificates screen would refresh.  Open the Certificates in MMC (Local Machine) and inspecting the Web Hosting gave a clue, the new certificate was there, but with a key - the private key was missing.  Could be because the original certificate was created on a completely different machine and imported to this new server.  At any rate, a simple certutil command fixed it .  A tip I received from  SSL disappears from the certificate list on Windows server - SSL Certificates - Namecheap.com Key steps are:  Double-click the certificate and go to  Details  tab. In certificate details locate the  Serial Number  field, click on it and copy its value. Open Command Prompt, pressing  Win+R  and typing  cmd , then click  OK In the command prompt type: ...

Ever need to reset a password in Bonobo Git Server ?

So, you've forgotten your password to bonobo git. Step 1: Get access to the sqlite file, probably called something like  Bonobo.Git.Server.db, sitting in the "wwwroot\Bonobo.Git.Server\App_Data" directory. Step 2: Using another tool, generate an md5 hash of your new desired password (as far as I know, sqlite does not have md5 capability) Step 3: Back in sqlite, using SQL, update the relevant user record, something like update User set Password = UPPER( 'thenewMD5hash') where Username = 'admin' ; Step 4: That's it, you are done, log in with your newly found password.

Save Attachments in Outlook automatically

For years I have wanted something to do this, and finally found it. Worked perfectly for me in Outlook 2013  In the end it is so simple. Guide from http://www.pixelchef.net/content/rule-autosave-attachment-outlook and https://msdn.microsoft.com/en-us/library/ee814736.aspx Open the VBA IDE in Outlook. Alt-F11 will do this. Insert the following code to the Modules section. On the left side there is a tree, expand until you find Modules. Then, if there is not a Module item under Modules, create one by right clicking on Modules. Or right click and choose Insert -> Module. Now, paste the text below in the main VBA window. Close the VBA IDE. Create a Rule that calls the script. Tools -> Rules and Alerts -> New Rule... In the first screen of the new rule wizard, choose "Check messages when they arrive". In the second, you could specify certain criteria that the message must match. Tip: Try "with specific words in the message header" and ...