[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 315
  • Last Modified:

.snk files for COM interop: best practices

Our company makes several assemblies that must be used from COM applications. Should we generate .snk files for each assembly, or is it advisable to sign all of our COM-aware assemblies with a single .snk file?
0
k3n51mm
Asked:
k3n51mm
  • 2
  • 2
2 Solutions
 
DEEPESHCommented:
It is advisable to generate snk for each assembly as they will be unique identifier for these objects, and when you register your >net component in registry through regasm, it plays major role in registry.
0
 
k3n51mmAuthor Commented:
one of our developers has come up with the idea that we should sign all of our software with the same key. I thought the .snk file was just key that was used to sign a component, and not the componenet's GUID. Can I get more of an explanation?
0
 
Joe_GriffithCommented:
One snk is all you should ever use. It has nothing to do with registering anything. I read somewhere that Microsoft only has 3 snk's for there entire line of products.
0
 
k3n51mmAuthor Commented:
Thanks Joe, can you point me to some documentation for this?
0
 
Joe_GriffithCommented:
Sorry, no. Have no idea where I read that about MS. I've always used a single SNK. There is another school of thought, however...

The point of the SNK is to insure that your code has not been changed. Some people feel that you should use a separate snk for each assembly so that if one is compromised they won't all be. Seems dumb to me but you should control whatever snk's you create carefully.

0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now