Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. Generation of Strong Names (Best practices??)

Generation of Strong Names (Best practices??)

Scheduled Pinned Locked Moved .NET (Core and Framework)
dotnetquestion
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    Paul Farry
    wrote on last edited by
    #1

    Guys, Just wondering if there are any documents on the generation of strong names for assemblies. Is it the norm to : a) Generate a strong name file for each and every assembly you want to put in the GAC b) Generate a company/personal one(and only 1), and use that against each and every assembly you want to put in the GAC or is there some other method that is employed?

    S 1 Reply Last reply
    0
    • P Paul Farry

      Guys, Just wondering if there are any documents on the generation of strong names for assemblies. Is it the norm to : a) Generate a strong name file for each and every assembly you want to put in the GAC b) Generate a company/personal one(and only 1), and use that against each and every assembly you want to put in the GAC or is there some other method that is employed?

      S Offline
      S Offline
      Steven Campbell
      wrote on last edited by
      #2

      I don't know what the norm is, but I can say what I do. I generate a single keyfile for use by everything I do for a company, whether or not it will go in the GAC. (You never know when you will want to put something there). Depending on your environment, you may want to delay-sign the assemblies, and then complete the signing later with a super-secret key file accessible only to trusted people. (I have not needed to do that yet).


      my blog

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups