DeleteReparsePoint Event

Fires when the OS wants to delete a reparse point from a file or directory.


virtual int FireDeleteReparsePoint(CBFSDeleteReparsePointEventParams *e);
typedef struct {
const char *FileName;
const void *ReparseBuffer;
int ReparseBufferLength;
int64 HandleInfo;
void *FileContext;
void *HandleContext;
int ResultCode; int reserved; } CBFSDeleteReparsePointEventParams;
virtual INT FireDeleteReparsePoint(CBFSDeleteReparsePointEventParams *e);
typedef struct {
LPCVOID ReparseBuffer;
INT ReparseBufferLength;
LONG64 HandleInfo;
LPVOID FileContext;
LPVOID HandleContext;
INT ResultCode; INT reserved; } CBFSDeleteReparsePointEventParams;


This event fires when the OS wants to delete a reparse point from the file or directory specified by FileName.

This event only needs to be handled if the UseReparsePoints property is enabled. To handle this event properly, applications must delete the reparse point data (and tag) stored previously for the specified file or directory. Any other actions taken in an earlier SetReparsePoint event should also be reversed appropriately. Note that the file or directory itself should not be deleted.

Please refer to the Reparse Points topic for more information.

The existing reparse point data is provided in this event as a convenience for use-cases that wish to utilize it.

The HandleInfo parameter carries a handle to an object with information about the file handle. While within the event handler, it can be used to call any of the following methods: GetHandleCreatorProcessId, GetHandleCreatorProcessName, GetHandleCreatorThreadId, or GetHandleCreatorToken.

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.

Please refer to the Buffer Parameters topic for more information on how to work with memory buffer event parameters.

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.

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