This documentation is archived and is not being maintained.

EnvironmentPermissionAttribute Class

Allows security actions for EnvironmentPermission 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 EnvironmentPermissionAttribute : 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 EnvironmentPermissionAttribute extends CodeAccessSecurityAttribute
SerializableAttribute 
ComVisibleAttribute(true) 
AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple=true, Inherited=false) 
public final class EnvironmentPermissionAttribute 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.

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 C#, 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 have EnvironmentPermission. Demands are typically made in managed libraries (DLLs) to help protect methods or classes from potentially harmful code.

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

/** @attribute 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 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
Show: