EnvironmentPermissionAttribute Class
Assembly: mscorlib (in mscorlib.dll)
'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 'Usage Dim instance As EnvironmentPermissionAttribute
/** @attribute SerializableAttribute() */ /** @attribute AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple=true, Inherited=false) */ /** @attribute ComVisibleAttribute(true) */ public final class EnvironmentPermissionAttribute extends CodeAccessSecurityAttribute
SerializableAttribute AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple=true, Inherited=false) ComVisibleAttribute(true) 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 example of a declarative attribute shows the correct way to request EnvironmentPermission for the ability to read the specified environment variables and states that you must have at least this permission to run your 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 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 EnvironmentPermission at link time. 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
/** @attribute EnvironmentPermissionAttribute(SecurityAction.Demand,
Unrestricted = true)
*/
System.Attribute
System.Security.Permissions.SecurityAttribute
System.Security.Permissions.CodeAccessSecurityAttribute
System.Security.Permissions.EnvironmentPermissionAttribute
Windows 98, Windows 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 .NET Framework does not support all versions of every platform. For a list of the supported versions, see System Requirements.