CBFS Filter 2020 C++ Builder Edition

Questions / Feedback?

AfterCanFileBeDeleted Event

Fires after the filesystem determines whether a file or directory can be deleted.

Syntax

typedef struct {
  String FileName;
  bool CanDelete;
  int Status;
  void* FileContext;
  void* HandleContext;
  int ResultCode;
} TcbfCBFilterAfterCanFileBeDeletedEventParams;

typedef void __fastcall (__closure *TcbfCBFilterAfterCanFileBeDeletedEvent)(System::TObject* Sender, TcbfCBFilterAfterCanFileBeDeletedEventParams *e);

__property TcbfCBFilterAfterCanFileBeDeletedEvent OnAfterCanFileBeDeleted = { read=FOnAfterCanFileBeDeleted, write=FOnAfterCanFileBeDeleted };

Remarks

This event fires after 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 only need to handle this event if they've added a standard filter rule that includes the FS_CE_AFTER_CAN_DELETE flag.

The CanDelete parameter reflects whether the file or directory can be deleted.

The Status parameter contains an NT status code that indicates the outcome of the operation; 0 indicates success. To convert this value to a Win32 error code, call the NtStatusToWin32Error method. Please note that this event won't fire for failed requests unless the ProcessFailedRequests property is enabled. Applications may change this parameter's value if they want a different NT status code to be returned.

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.

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.

 
 
Copyright (c) 2020 Callback Technologies, Inc. - All rights reserved.
CBFS Filter 2020 C++ Builder Edition - Version 20.0 [Build 7543]