SetReparsePoint Event

Fires when the OS wants to create or update a reparse point on a file or directory.


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


This event fires when the OS wants to create or update a reparse point on 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 store the given reparse point data and tag, and associate them with the specified file or directory, in their backend storage. Both pieces of information are needed for the application to correctly handle any future GetFileInfo and EnumerateDirectory events concerning the specified file or directory.

Please refer to the Reparse Points topic for more information.

The ReparseTag parameter specifies the reparse point's tag, which is the value the system uses to identify the format of the reparse point data. This value is also present in the ReparseBuffer data; the class extracts it and provides it separately for convenience.

The ReparseBuffer parameter points to a memory buffer that contains the full reparse point data. The ReparseBufferLength parameter specifies the length, in bytes, of ReparseBuffer.

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

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.

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]