Allows security actions for EnvironmentPermission to be applied to code using declarative security. This class cannot be inherited.
(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 EnvironmentPermissionAttribute _
Inherits CodeAccessSecurityAttribute
Dim instance As EnvironmentPermissionAttribute
[SerializableAttribute]
[AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple = true,
Inherited = false)]
[ComVisibleAttribute(true)]
public sealed class EnvironmentPermissionAttribute : CodeAccessSecurityAttribute
[SerializableAttribute]
[AttributeUsageAttribute(AttributeTargets::Assembly|AttributeTargets::Class|AttributeTargets::Struct|AttributeTargets::Constructor|AttributeTargets::Method, AllowMultiple = true,
Inherited = false)]
[ComVisibleAttribute(true)]
public ref class EnvironmentPermissionAttribute sealed : public CodeAccessSecurityAttribute
public final class EnvironmentPermissionAttribute extends CodeAccessSecurityAttribute
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.
Environment variable names are case-insensitive. Multiple environment variable names are specified by separating the names using PathSeparator.
The following code example demonstrates how to request the EnvironmentPermission by using the EnvironmentPermissionAttribute class, indicating that at a minimum this permission is required to run the code.
<Assembly: EnvironmentPermissionAttribute(SecurityAction.RequestMinimum, _
Read := "COMPUTERNAME;USERNAME;USERDOMAIN")>
'In Visual Basic, you must specify that you are using the assembly scope when making a request.
[assembly:EnvironmentPermissionAttribute(SecurityAction.RequestMinimum,
Read="COMPUTERNAME;USERNAME;USERDOMAIN")]
//In C#, you must specify that you are using the assembly scope when making a request.
[assembly:EnvironmentPermissionAttribute(SecurityAction::RequestMinimum,
Read="COMPUTERNAME;USERNAME;USERDOMAIN")];
//In C++, 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 have EnvironmentPermission. Demands are typically made in managed libraries (DLLs) to help protect methods or classes from potentially harmful code.
<EnvironmentPermission(SecurityAction.Demand, Unrestricted := True)> _
Public Class SampleClass
[EnvironmentPermissionAttribute(SecurityAction.Demand, Unrestricted=true)]
[EnvironmentPermissionAttribute(SecurityAction::Demand,Unrestricted=true)]
System..::.Object
System..::.Attribute
System.Security.Permissions..::.SecurityAttribute
System.Security.Permissions..::.CodeAccessSecurityAttribute
System.Security.Permissions..::.EnvironmentPermissionAttribute
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