Allows security actions for PublisherIdentityPermission to be applied to code using declarative security. This class cannot be inherited.
Namespace:
System.Security.Permissions
Assembly:
mscorlib (in mscorlib.dll)
Visual Basic (Declaration)
<SerializableAttribute> _
<AttributeUsageAttribute(AttributeTargets.Assembly Or AttributeTargets.Class Or AttributeTargets.Struct Or AttributeTargets.Constructor Or AttributeTargets.Method, AllowMultiple := True, _
Inherited := False)> _
<ComVisibleAttribute(True)> _
Public NotInheritable Class PublisherIdentityPermissionAttribute _
Inherits CodeAccessSecurityAttribute
Dim instance As PublisherIdentityPermissionAttribute
[SerializableAttribute]
[AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple = true,
Inherited = false)]
[ComVisibleAttribute(true)]
public sealed class PublisherIdentityPermissionAttribute : CodeAccessSecurityAttribute
[SerializableAttribute]
[AttributeUsageAttribute(AttributeTargets::Assembly|AttributeTargets::Class|AttributeTargets::Struct|AttributeTargets::Constructor|AttributeTargets::Method, AllowMultiple = true,
Inherited = false)]
[ComVisibleAttribute(true)]
public ref class PublisherIdentityPermissionAttribute sealed : public CodeAccessSecurityAttribute
public final class PublisherIdentityPermissionAttribute extends CodeAccessSecurityAttribute
The scope of the declaration that is allowed depends on the SecurityAction that is used.
The properties CertFile, SignedFile, and X509Certificate are mutually exclusive.
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.
Important Note: |
|---|
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, identity permissions can have any permission state value. This means that in version 2.0, identity permissions have the same behavior as permissions that implement the IUnrestrictedPermission interface. For information on executing version 2.0 applications with version 1.1 code access security (CAS) policy, see <legacyV1CASPolicy> Element. |
Note: |
|---|
By default, code access security does not check for Publisher evidence. Unless your computer has a custom code group based on the PublisherMembershipCondition class, you can improve performance by bypassing Authenticode signature verification. This is accomplished by configuring the runtime to not provide Publisher evidence for code access security. For more information about how to configure this option and which applications can use it, see the <generatePublisherEvidence> element. |
The following example of a declarative attribute shows the correct way to request PublisherIdentityPermission and states that you must have at least this permission to run your code. Code will only execute if signed with the Authenticode X.509v3 publisher certificate stored in the file "myX509.cer".
<Assembly: PublisherIdentityPermissionAttribute(SecurityAction.RequestMinimum, CertFile := "MyX509.cer")>
'In Visual Basic, you must specify that you are using the assembly scope when making a request.
[assembly:PublisherIdentityPermissionAttribute(SecurityAction.RequestMinimum, CertFile = "MyX509.cer")]
//In C#, you must specify that you are using the assembly scope when making
//a request.
[assembly:PublisherIdentityPermissionAttribute( SecurityAction::RequestMinimum, CertFile="MyX509.cer" )];
//In C++, you must specify that you are using the assembly scope when making
//a request.
System..::.Object
System..::.Attribute
System.Security.Permissions..::.SecurityAttribute
System.Security.Permissions..::.CodeAccessSecurityAttribute
System.Security.Permissions..::.PublisherIdentityPermissionAttribute
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.
Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98
The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.
.NET Framework
Supported in: 3.5, 3.0, 2.0, 1.1, 1.0
Reference
Other Resources