Windows Dev Center

Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

SecurityPermissionAttribute Class

Allows security actions for SecurityPermission to be applied to code using declarative security. This class cannot be inherited.

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

[SerializableAttribute] 
[ComVisibleAttribute(true)] 
[AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple=true, Inherited=false)] 
public sealed class SecurityPermissionAttribute : CodeAccessSecurityAttribute
/** @attribute SerializableAttribute() */ 
/** @attribute ComVisibleAttribute(true) */ 
/** @attribute AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple=true, Inherited=false) */ 
public final class SecurityPermissionAttribute extends CodeAccessSecurityAttribute
SerializableAttribute 
ComVisibleAttribute(true) 
AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple=true, Inherited=false) 
public final class SecurityPermissionAttribute extends CodeAccessSecurityAttribute
Not applicable.

The scope of the declaration that is allowed depends on the SecurityAction that is used.

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.

When you use the SecurityPermissionAttribute class, follow the security action with the permission(s) that are being requested. Each security permission that can be requested, as defined in the SecurityPermissionFlag enumeration, has a corresponding property in the SecurityPermissionAttribute class. For example, to demand the ability to access unmanaged code, follow the demand statement with the property setting that is being requested, as follows: SecurityPermissionAttribute(SecurityAction.Demand, UnmanagedCode=true).

NoteNote:

An exception to the equivalence between the SecurityPermissionFlag enumeration and the SecurityPermissionAttribute properties is that the AllFlags enumeration value is represented by the Unrestricted property (inherited from the SecurityAttribute class). To demand all security permissions, specify Unrestricted=true.

The following example of a declarative attribute shows the correct way to request SecurityPermission for the ability to assert and states that you must have at least this permission to run your code.

[assembly:SecurityPermissionAttribute(SecurityAction.RequestMinimum, Assertion=true)]
//In C#, you must specify that you are using the assembly scope when making a request.

/** @assembly SecurityPermissionAttribute(SecurityAction.RequestMinimum, 
    Assertion = true)
 */
// In VJ#, you must specify that you are using the assembly scope
// when making a request.

The following example shows how to demand that the calling code has SecurityPermission at link time. Demands are typically made in managed libraries (DLLs) to help protect methods or classes from potentially harmful code.

[SecurityPermissionAttribute(SecurityAction.Demand, Unrestricted=true)]

/** @attribute SecurityPermissionAttribute(SecurityAction.Demand, 
    Unrestricted = true)
 */

For a complete example showing how to create instances of the SecurityPermissionAttribute class that are used to deny and demand security permissions see the SecurityPermissionAttribute constructor.

System.Object
   System.Attribute
     System.Security.Permissions.SecurityAttribute
       System.Security.Permissions.CodeAccessSecurityAttribute
        System.Security.Permissions.SecurityPermissionAttribute

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 98, Windows Server 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition

The Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.

.NET Framework

Supported in: 3.0, 2.0, 1.1, 1.0

Community Additions

Show:
© 2015 Microsoft