What is the process for strong naming an assembly

Question

Hi...... Ques:Hello friends now i have work on assembly in asp.net please explain What is the process for strong naming an assembly ? or What is the purpose of strong naming tool ( sn.exe ) in .NET ?

lakshmipathi vemula · Answer

hi.. your explanation in strong naming helped me alot..thanks...

Sandeep Soni · Answer

Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable{mso-style-name:"Table Normal";mso-tstyle-rowband-size:0;mso-tstyle-colband-size:0;mso-style-noshow:yes;mso-style-priority:99;mso-style-qformat:yes;mso-style-parent:"";mso-padding-alt:0in 5.4pt 0in 5.4pt;mso-para-margin-top:0in;mso-para-margin-right:0in;mso-para-margin-bottom:10.0pt;mso-para-margin-left:0in;line-height:115%;mso-pagination:widow-orphan;font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ascii-font-family:Calibri;mso-ascii-theme-font:minor-latin;mso-fareast-font-family:"Times New Roman";mso-fareast-theme-font:minor-fareast;mso-hansi-font-family:Calibri;mso-hansi-theme-font:minor-latin;mso-bidi-font-family:"Times New Roman";mso-bidi-theme-font:minor-bidi;} Providing Strong name to an assembly: ->Solution Explorer ->Class Library1 ->Properties. ->Select Signing tab -> Check the Sign assembly Check Box ->Select In the dialogue box(Create a Strongname Key)->Enter the Strong name Key in key file name ->click OK ->Demo.snk will be added in the Classlibrary1 project Now click on Application Tab and click on Assembly Information button Now Assembly Information dialogbox will open.Default version for Assembly Version will be 1.0.0.0 (Major.Minor.Build.revision),Keep it as it is and ensure None is selected in Neutral language.Now Click OK. Strongname=Assemblyname+Version+Public/Private Key+Culture Purpose of Strong naming: The purpose is that we can make an assembly as shared assembly so that there will be no confusion when we move that to GAC. For more information on Assemblies and GAC http://www.bestdotnettraining.com/Online/Training/CSharp/Working-with-Components-Or-Assemblies/11

Satyapriya Nayak · Answer

Hi Manish, In .NET, the assembly name usually consists of 4 parts as listed below. 1. Simple Textual Name 2. Version Number (The version number is also divided into 4 parts) 3. Culture 4. Public Key Token If an assembly contains, all the 4 parts, then the assembly is a strongly named assembly, other wise the assembly is called as a weak named assembly. In general, when you compile any .NET application, the generated assembly by default will have the Simple Textual Name, Version Number and Culture but not the public key token. If you have to sign the assembly with a public key token, you first have to generate the key pair using key generation tool called strong naming tool (sn.exe). The generated key pair will consist of a private and a public key and are written into a key file. Key files have the extension of .snk. We now have to associate the key file with the project, so that when we compile the project, the generated assembly is signed using the key pair. To do this, In AssemblyInfo.cs file of the project, specify AssemblyKeyFile attribute as shown below. [assembly: AssemblyKeyFile("MyKey.snk")] The last and final step is to build the project which will automatically sign the assembly using the key file. This process generates the strongly named assembly. In short, there are 3 simple steps to generate a strongly named assembly. 1. Generate the key pair using strong naming tool, SN.exe. 2. Associate the generated Key file to the project using AssemblyKeyFile, which is present in AssemblyInfo.cs file. 3. Build the project. Once, you have strongly named the assembly, you can copy it to GAC. There are 2 ways to copy an assembly into GAC. 1. Using simple drag and drop : Drag the generated assembly into the GAC folder. Usually the path for GAC is c:\windows\assembly. On some machines this could be c:\winnt\assembly. 2. Use GAC utility : Use GAC Utility tool(gacutil.exe) as shown below in visual studio command prompt. gacutil.exe -i C:\MyAssembly.dll (- i stands for install) Once, you have successfuly copied the assembly into GAC, notice the four parts of the assembly name. The culture column could be empty, indicating that the assembly is language neutral. Refer http://venkataspinterview.blogspot.com/2011/06/what-is-process-for-strong-naming.html Thanks

What is the process for strong naming an assembly

Answers (3)