0

I am trying to find the right way to set up my SharePoint solution with miltiple projects (in VS2012). In that, I am having difficulty understanding the concept of reusing the strong name key file.

One particular thing that I cannot wrap my head around is using one .snk file for a company's solutions. But if you are doing that, wouldnt that mean the version information will also be shared among the projects that share the key file? Different SharePoint projects could have different versions. So, how does this setup work?

Some of the urls that I have refered to so far:

1 Answer 1

2

The key file only determines the PublicKeyToken part of the full assembly name. The version name remains specific to each project and can be set independently.

2
  • So, .snk is the part of strong name of an assembly? Then in VS, what components are part of strong name? So far I have, .snk file and AssemblyInfo.cs. And how does the private key come into play?
    – Tom
    Commented Dec 18, 2013 at 16:37
  • What do you mean exactly with private key and how would you like to use it for signing assemblies? What is it that you are trying to achieve? Commented Dec 27, 2013 at 8:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.