At a glance to the subjected topic, someone can argue, to deploy a third party assembly first it has to be signed with a valid strong name that is unique in time and space. How can an untrusted assembly be signed with a a valid public key cryptographic keys? As, the word IMPOSSIBLE contains the word POSSIBLE, there’s a way to sign a third party dll with a strong name and ultimately it is allowed to deploy that into Global Assembly Cache (GAC) .
In one of my project assignments, I had to deploy a third party assembly into GAC. The following are the steps that I’ve followed.
- First, generate a key file using “SN.exe” utility that is provided by .NET framework.
(myKeyFile.snk is the name of the key which stores under the GACDemo folder of C:\ drive)
Early Bites 