.NET: Strong naming vs. Authenticode

Question

Having read about strong names in .NET here, for example, I have the following question:

We have an Authenticode code signing certificate with which

Answer 1

The answer will depend upon why you have created a strong name - the intended use of strong name is to create a unique identity for the assembly. For example, if you need to push your assembly in GAC then strong name is must. However strong name is not really meant for verifying the authenticity of publisher - Authenticode serve that purpose. See this article: http://blogs.msdn.com/b/shawnfa/archive/2005/12/13/authenticode-and-assemblies.aspx