Assemblies resigned/recompiled when referenced assembly patched

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

A question from my client concerning assembly signing conventions:

In order to get our main code to run inside of .NET Enterprise Services, we
need to give it (and all other assemblies referenced by our main code) a
strong name key. We know how to do this by running SN -K and then setting
the AssemblyKeyFile attribute in the AssemblyInfo.cs file.

A question comes when and if we need to make a patch release. Our main
assembly references a utility assembly, shared by other assemblies. If we
put out a patch release of our main assembly, we would update its version,
but what about the key information? Would we need to give it a new public
key token as well? If so, do we need to rebuild all of our assemblies
against this new assembly with the new version and key?
 
If we put out a patch release of our main assembly, we would update its version,
but what about the key information? Would we need to give it a new public
key token as well?
Click to expand...

No, keep using the same key.


Mattias
 
Back
Top