This documentation is archived and is not being maintained.

SecurityPermissionAttribute Class

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

For a list of all members of this type, see SecurityPermissionAttribute Members.


[Visual Basic]
<AttributeUsage(AttributeTargets.Assembly Or AttributeTargets.Class _
   Or AttributeTargets.Struct Or AttributeTargets.Constructor Or _
NotInheritable Public Class SecurityPermissionAttribute
   Inherits CodeAccessSecurityAttribute
[AttributeUsage(AttributeTargets.Assembly | AttributeTargets.Class
   | AttributeTargets.Struct | AttributeTargets.Constructor |
public sealed class SecurityPermissionAttribute :
[AttributeUsage(AttributeTargets::Assembly |
   AttributeTargets::Class | AttributeTargets::Struct |
   AttributeTargets::Constructor | AttributeTargets::Method)]
public __gc __sealed class SecurityPermissionAttribute : public
   AttributeUsage(AttributeTargets.Assembly | AttributeTargets.Class |
   AttributeTargets.Struct | AttributeTargets.Constructor |
class SecurityPermissionAttribute extends

Thread Safety

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


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.


[Visual Basic, C#, C++] 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.

[Visual Basic] 
<Assembly:SecurityPermissionAttribute(SecurityAction.RequestMinimum, _
Assertion := True)>
'In Visual Basic, you must specify that you are using the assembly scope when making a request.

[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 C++, you must specify that you are using the assembly scope when making a request.

[Visual Basic, C#, C++] 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.

[Visual Basic] 
<SecurityPermissionAttribute(SecurityAction.Demand, _
 Unrestricted := True)> Public Class SampleClass

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

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

[JScript] No example is available for JScript. To view a Visual Basic, C#, or C++ example, click the Language Filter button Language Filter in the upper-left corner of the page.


Namespace: System.Security.Permissions

Platforms: Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family

Assembly: Mscorlib (in Mscorlib.dll)

See Also

SecurityPermissionAttribute Members | System.Security.Permissions Namespace | Extending Metadata Using Attributes | SecurityPermission | SecurityPermissionFlag