AfterSetFileSize Event

Fires after a file is resized.

Syntax

• C#
• VB.NET

public event OnAfterSetFileSizeHandler OnAfterSetFileSize;

public delegate void OnAfterSetFileSizeHandler(object sender, CbfilterAfterSetFileSizeEventArgs e);

public class CbfilterAfterSetFileSizeEventArgs : EventArgs {
  public string FileName { get; }
  public long Size { get; }
  public int Status { get; set; }
  public IntPtr FileContext { get; set; }
  public IntPtr HandleContext { get; set; }
  public int ResultCode { get; set; }
}

Public Event OnAfterSetFileSize As OnAfterSetFileSizeHandler

Public Delegate Sub OnAfterSetFileSizeHandler(sender As Object, e As CbfilterAfterSetFileSizeEventArgs)

Public Class CbfilterAfterSetFileSizeEventArgs Inherits EventArgs
  Public ReadOnly Property FileName As String
  Public ReadOnly Property Size As Long
  Public Property Status As Integer
  Public Property FileContext As IntPtr
  Public Property HandleContext As IntPtr
  Public Property ResultCode As Integer
End Class

Remarks

This event fires after the file specified by FileName is resized, whether explicitly (e.g., truncation) or implicitly (i.e., as data is appended).

Applications only need to handle this event if they've added a standard filter rule that includes the FS_CE_AFTER_SET_SIZES flag.

The Size parameter reflects the new file size, in bytes.

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. (If the system's cache manager or memory manager initiated the operation, HandleContext may be absent, in which case it will be IntPtr.Zero.)

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.