| **Navigation:**  Project System > Project Properties - Clarion.NET(Clarion#) >====== Signing ====== | [[icsharpcode sharpdevelop gui optionpanels referencepaths.htm|{{btn_prev_n.gif|Previous page}}]][[coming future.htm|{{btn_home_n.gif|Return to chapter overview}}]][[project options asp net.htm|{{btn_next_n.gif|Next page}}]] |
|  ||

{{projpropscnet_shg.jpg|ProjPropsCNet_shg.jpg}}[[icsharpcode sharpdevelop gui optionpanels debugoptions.htm|]][[softvelocity clarionnet binding optionpanels buildoptions.htm|]][[icsharpcode sharpdevelop gui optionpanels buildevents.htm|]][[icsharpcode sharpdevelop gui optionpanels signing.htm|]][[softvelocity clarionnet binding optionpanels includepaths.htm|]][[icsharpcode sharpdevelop gui optionpanels referencepaths.htm|]][[softvelocity clarionnet binding optionpanels applicationsettings.htm|]]

Strong-name signing gives a software component a globally unique identity that cannot be spoofed by someone else. Strong names are used to guarantee that component dependencies and configuration statements map to exactly the right component and component version.

A strong name consists of the assembly's identity (simple text name, version number, and culture information), plus a public key token and a digital signature. Check the **Sign the Assembly **check box to create or select a strong name.

In the **Choose a string name key file** drop list, select //<;Create'>// to create a key file, or //<;Browse'>// to select an existing one.

Check the **Delay Sign only** check box to delay sign the assembly. When you request a fully signed assembly, the compiler hashes the file that contains the manifest (assembly metadata) and signs that hash with the private key. The resulting digital signature is stored in the file that contains the manifest. When an assembly is delay signed, the linker does not compute and store the signature, but reserves space in the file so the signature can be added later.