Defines the identity permission for strong names. This class cannot be inherited.
Assembly: mscorlib (in mscorlib.dll)
Initializes a new instance of the PermissionState.class with the specified
|StrongNameIdentityPermission(StrongNamePublicKeyBlob, String, Version)|
Initializes a new instance of theclass for the specified strong name identity.
Declares that the calling code can access the resource protected by a permission demand through the code that calls this method, even if callers higher in the stack have not been granted permission to access the resource. Using Assert can create security issues.(Inherited from CodeAccessPermission.)
Creates and returns an identical copy of the current permission.(Overrides CodeAccessPermission.Copy().)
Obsolete. Prevents callers higher in the call stack from using the code that calls this method to access the resource specified by the current instance.(Inherited from CodeAccessPermission.)
Reconstructs a permission with a specified state from an XML encoding.(Overrides CodeAccessPermission.FromXml(SecurityElement).)
Creates and returns a permission that is the intersection of the current permission and the specified permission.(Overrides CodeAccessPermission.Intersect(IPermission).)
Determines whether the current permission is a subset of the specified permission.(Overrides CodeAccessPermission.IsSubsetOf(IPermission).)
Prevents callers higher in the call stack from using the code that calls this method to access all resources except for the resource specified by the current instance.(Inherited from CodeAccessPermission.)
Creates and returns a string representation of the current permission object.(Inherited from CodeAccessPermission.)
Creates an XML encoding of the permission and its current state.(Overrides CodeAccessPermission.ToXml().)
Creates a permission that is the union of the current permission and the specified permission.(Overrides CodeAccessPermission.Union(IPermission).)
Starting with the .NET Framework 4, identity permissions are not used.
In the .NET Framework versions 1.0 and 1.1, identity permissions cannot have an Unrestricted permission state value. In the .NET Framework version 2.0 and later, identity permissions can have any permission state value. This means that in version 2.0 and later versions, identity permissions have the same behavior as permissions that implement the IUnrestrictedPermission interface. That is, a demand for an identity always succeeds, regardless of the identity of the assembly, if the assembly has been granted full trust.
Use StrongNameIdentityPermissionAttribute attribute succeed only if the immediate caller has the correct evidence.to confirm that the calling code is in a particular strong-named code assembly. Full demands for succeed only if all the assemblies in the stack have the correct evidence to satisfy the demand. Link demands that use the
A strong name identity is based on a cryptographic public key called a binary large object (BLOB), which is optionally combined with the name and version of a specific assembly. The key defines a unique namespace and provides strong verification that the name is genuine, because the definition of the name must be in an assembly that is signed by the corresponding private key.
Note that the validity of the strong name key is not dependent on a trust relationship or on any certificate necessarily being issued for the key.
In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective even when the calling assembly is fully trusted. That is, even if the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. In the .NET Framework version 2.0 and later, demands for identity permissions are ineffective if the calling assembly has full trust. This ensures consistency for all permissions and eliminates the treatment of identity permissions as a special case.
The StrongNameIdentityPermissionAttribute attribute can be used to define strong-name requirements at the assembly level. In the .NET Framework version 2.0 and later, you can also use the InternalsVisibleToAttribute attribute to specify that all nonpublic types in that assembly are visible to another assembly. For more information, see Friend Assemblies (C# and Visual Basic).class is used to define strong-name requirements for accessing the public members of a type. The
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.