signcode.exe prevent popup? (X509 SPC)

From: Claus Konrad (no_at_spam.thanks)
Date: 06/14/05

  • Next message: Claus Konrad: "Re: Using an updated or newer assembly?" 
    Date: Tue, 14 Jun 2005 00:22:58 +0200

    Hi

    When signing an assembly with an X509 Certificate, the signcode application
    always prompts you for the private key password to verify you know that.

    I would like to automate this process so that my assemblies are signed
    automatically after each nightly build. How is that possible?

    /Claus Konrad

  • Next message: Claus Konrad: "Re: Using an updated or newer assembly?"

    Relevant Pages

    • Re: signcode.exe prevent popup? (X509 SPC)
      ... I included the signing in the post build step, ... Claus Konrad wrote: ... > I would like to automate this process so that my assemblies are ...
      (microsoft.public.dotnet.security)
    • Re: Is there a .NET compiler ?
      ... It is possible to automate the NGEN. ... copies the new one, register it in GAC, then NGEN's it. ... We have over 200 assemblies in our application and this is the approach ... our 50+ Developers in sync during dev. ...
      (borland.public.delphi.non-technical)
    • Re: assembly verification
      ... A strong name is used by the CLR to verify that an assembly's contents match ... those at the time of its signing. ... As for the assemblies that are being loaded, ... > The application will operate in a rather wild environment, ...
      (microsoft.public.dotnet.security)
    • Latebinded assemblies: strongname verification
      ... I am having a a plugin-framework, where I need to load assemblies (the ... How can I verify the keypair of a loaded assembly? ...
      (microsoft.public.dotnet.languages.csharp)
    • Latebinded assemblies: strongname verification
      ... I am having a a plugin-framework, where I need to load assemblies (the ... How can I verify the keypair of a loaded assembly? ...
      (microsoft.public.dotnet.security)
    • Quantcast