Allows security actions for System.Security.Permissions.StrongNameIdentityPermission to be applied to code using declarative security. This class cannot be inherited.
Starting with the net_v40_long, identity permissions are not used.
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, although 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 assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.
The scope of the declaration that is allowed depends on the System.Security.Permissions.SecurityAction that is used. You can obtain the key string for this attribute by running the Strong Name tool (Sn.exe) with the token and public key options (Sn -tp keyfile) against a file that has an Authenticode signature. For more information, see Sn.exe (Strong Name Tool).
The security information declared by a security attribute is stored in the metadata of the attribute target and is accessed by the system at run time. Security attributes are used only for declarative security. For imperative security, use the corresponding permission class.
The System.Security.Permissions.StrongNameIdentityPermissionAttribute attribute can be used to define strong-name requirements for access to public members at the assembly level. In the .NET Framework version 2.0 and later, you can also use the System.Runtime.CompilerServices.InternalsVisibleToAttribute attribute to specify that all nonpublic types in that assembly are visible to another assembly. For more information, see Friend Assemblies (C# Programmer's Reference) or Friend Assemblies (Visual Basic).