The PermissionState enumeration has values indicating whether a permission should have all or no access at creation.
[Visual Basic] Public Enum PermissionState [C#] public enum PermissionState [C++] public enum PermissionState
[JScript] In JScript, you can use the enumerations in the NGWS frameworks, but you cannot define your own.
Permissions are created in either a totally restrictive (no permission) or totally unrestrictive (all permissions corresponding to the particular resource) state. For example, the file permission constructor would create an object representing either no access to any files or all access to all files. Each type of permission clearly defines extreme states representing either all or none of the permissions expressable within the type. Thus, it is possible to create a generic permission in a completely restricted or unrestricted state without knowledge of the particular permission, however intermediate states can only be set according to the specific permission semantics
All code access permission objects take a PermissionState value as an argument to their constructor.
Member Name | Description |
---|---|
None | Indicates no use of or access to the resource protected by the permission. |
Unrestricted | Indicates full use of or access to the resource protected by a permission. |
Namespace: System.Security.Permissions
Assembly: mscorlib.dll