FileDialogPermissionAttribute Class
Assembly: mscorlib (in mscorlib.dll)
[SerializableAttribute] [AttributeUsageAttribute(AttributeTargets::Assembly|AttributeTargets::Class|AttributeTargets::Struct|AttributeTargets::Constructor|AttributeTargets::Method, AllowMultiple=true, Inherited=false)] [ComVisibleAttribute(true)] public ref class FileDialogPermissionAttribute sealed : public CodeAccessSecurityAttribute
/** @attribute SerializableAttribute() */ /** @attribute AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple=true, Inherited=false) */ /** @attribute ComVisibleAttribute(true) */ public final class FileDialogPermissionAttribute extends CodeAccessSecurityAttribute
SerializableAttribute AttributeUsageAttribute(AttributeTargets.Assembly|AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, AllowMultiple=true, Inherited=false) ComVisibleAttribute(true) public final class FileDialogPermissionAttribute 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.
The following code example demonstrates how to request the FileDialogPermission by using the FileDialogPermissionAttribute class, indicating that at a minimum this permission is required to run the code.
[assembly:FileDialogPermissionAttribute(SecurityAction::RequestMinimum,Unrestricted=true)]; //In C++, you must specify that you are using the assembly scope when making a request.
/** @assembly FileDialogPermissionAttribute(SecurityAction.RequestMinimum,
Unrestricted = true)
*/
// In VJ#, you must specify that you are using the assembly scope when
// making a request.
The following code example demonstrates how to demand that the calling code have FileDialogPermission. Demands are typically made in managed libraries (DLLs) to help protect methods or classes from potentially harmful code.
/** @attribute FileDialogPermissionAttribute(SecurityAction.Demand,
Unrestricted = true)
*/
System.Attribute
System.Security.Permissions.SecurityAttribute
System.Security.Permissions.CodeAccessSecurityAttribute
System.Security.Permissions.FileDialogPermissionAttribute
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.