why use AssemblyDelaySign if u can install in GAC with any key?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

xamman - 09 Apr 2007 06:12 GMT

take as an example an organisation developing software where the
public key is known but the private key is kept by only the top
official.

why would you use AssemblyDelaySign and sign an assebly with only its
public key when a developer can generate a different pub/priv key pair
for himself and sign an assembly with that?

later when developer is done testing he can submit his asembly to the
top official for signing with organization key pair?am i missing
something here?

thx

Reply to this Message

Mattias Sjögren - 09 Apr 2007 07:59 GMT

>later when developer is done testing he can submit his asembly to the
>top official for signing with organization key pair?am i missing
>something here?

If you change keys you get an entirely different assembly name. That
breaks existing references, security settings and other configuration
options where you specify the assembly name. In other words, it could
become a maintainance mess.

Mattias

Signature

Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

Reply to this Message

xamman - 09 Apr 2007 19:36 GMT

thanks mattias. i knew there had to be a good reason

Reply to this Message

why use AssemblyDelaySign if u can install in GAC with any key?

Free Magazines