Fires before the filesystem determines whether a file or directory can be deleted.
The 'callback' is called when the 'BeforeCanFileBeDeleted' event is emited.
The argument 'e' has the following properties:
e.fileName e.canDelete e.fileContext e.handleContext e.processRequest e.resultCode
This event fires before the filesystem determines whether the file or directory specified by FileName can be deleted. Such determinations are made anytime the Windows API's NtSetInformationFile function is called with FILE_DISPOSITION_INFORMATION or FILE_DISPOSITION_INFORMATION_EX data (which occurs for both "normal" delete requests, and file create/open requests that include the FILE_FLAG_DELETE_ON_CLOSE flag).
Applications may handle the underlying request by setting CanDelete as desired and then setting ProcessRequest to false. Note that if a file is opened with the FILE_FLAG_DELETE_ON_CLOSE flag, then this event will be fired before BeforeCreateFile/BeforeOpenFile is fired, and setting the CanDelete parameter to false will prevent the file from being opened in the first place.
The CanDelete parameter specifies whether the file or directory can be deleted.
The FileContext and HandleContext parameters are placeholders for application-defined data associated with the file and specific handle, respectively. Please refer to the Contexts topic for more information. (If the specified file or directory was not opened before the request, both contexts will be absent, in which case these parameters will be .)
The ProcessRequest parameter controls whether the request is sent onwards for further processing by subsequent filter drivers and the filesystem; it is true by default.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource isn't available, security checks failed, etc.), set it to a non-zero value to report an appropriate error. Please refer to the Error Reporting and Handling topic for more information.
This event is fired synchronously; please refer to the Event Types topic for more information.