StrongName Class

StrongName Class


Provides the strong name of a code assembly as evidence for policy evaluation. This class cannot be inherited.

Namespace:   System.Security.Policy
Assembly:  mscorlib (in mscorlib.dll)

public sealed class StrongName : EvidenceBase, IIdentityPermissionFactory

System_CAPS_pubmethodStrongName(StrongNamePublicKeyBlob, String, Version)

Initializes a new instance of the StrongName class with the strong name public key blob, name, and version.


Gets the simple name of the current StrongName.


Gets the StrongNamePublicKeyBlob of the current StrongName.


Gets the Version of the current StrongName.


Creates a new object that is a copy of the current instance.(Overrides EvidenceBase.Clone().)


Creates an equivalent copy of the current StrongName.


Creates a StrongNameIdentityPermission that corresponds to the current StrongName.


Determines whether the specified strong name is equal to the current strong name.(Overrides Object.Equals(Object).)


Gets the hash code of the current StrongName.(Overrides Object.GetHashCode().)


Gets the Type of the current instance.(Inherited from Object.)


Creates a string representation of the current StrongName.(Overrides Object.ToString().)

The StrongName class represents evidence of a unique, cryptographically strong name of a code assembly. The strong name consists of a public key, a given name, and a version. The public key corresponds to the publisher's private key which is kept secret, and with which the assembly must be signed in order for the strong name to be valid.

Strong names are typically assigned to assemblies using either AssemblyKeyFileAttribute, AssemblyKeyNameAttribute or AssemblyDelaySignAttribute in conjunction with the SN utility (see Sn.exe (Strong Name Tool)).

StrongNameIdentityPermission uses this class to confirm that calling code is in a particular strong-named code assembly.

.NET Framework
Available since 1.1

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Return to top
© 2015 Microsoft