Strong naming or authentication signs new assembly

Question

I asked the end user to add Strong Naming to one of my components because they want to reference it from a strong named assembly.

I already have a certificate of authenticity, so I'm interested in making my component suitable for use by their strong named component, is it enough for me to simply sign the component with my authentication key?

Or do I have an assembly strong mark (using the Al.exe file) to be considered a strong name?

I cannot find the documentation for "vrs authenticode strong name" which is explicit regarding this.

Answer 1

You have no “use" strong name, regardless of whether you use the original signature. This is a choice, and it is usually completely orthogonal to the choice of applying the signature of the script. If you could provide more detailed information about your strong name signing goals, it would be much easier to give you a definitive answer about whether they will be addressed through the original signature ...

---

Updated the following supplement to the question ...

, . , ( , ).

Answer 2

Strongnaming Authenticode . Strongnaming , , () "" , . Authenticode PE ( Win32 EXE, DLL .NET ..). , .

. ( ), .