24 Apr 07 P92

Strongly named assembly and weakly named assembly

Strong Name Utility,SN.exe – [assembly:AssemblyKeyFile("fsyKey.keys")]

GAC – Global Assembly Cache C:\Windows\Assembly\GAC

GACUtil.exe

“(Version)_(Culture)_(PublicKeyToken)”

Response file :  on the command line prepended by an @ sign OR CSC.rsp OR /noconfig

Delayed Signing or partial signing. CSC.exe – AssemblyKeyAttribute and AssemblyDelaySignAttribute AL.exe /keyf[ile] or /delay[sign]

 

The following list summarizes the steps discussed in this section to develop your assembly

by using the delay signing technique:

1. While developing an assembly, obtain a file that contains only your company’s public key and add the following two attributes to your source code:

2. [assembly:AssemblyKeyFile("MyCompanyPublicKey.keys")]

[assembly:AssemblyDelaySign(true)]

3. After building the assembly, execute the following line so that you can install it in the GAC, build other assemblies that reference the assembly, and test the assembly.Note that you have to do this only once; it’s not necessary to perform this step each time you build your assembly.

SN.exe ÐVr MyAssembly.dll

4. When ready to package and deploy the assembly, obtain your company’s private key(key pair) and execute the following line:

SN.exe -R MyAssembly.dll MyCompany.keys

5. To test, turn verification back on by executing the following line:

SN -Vu MyAssembly.dll