AfterUnlockAll Event

Fires after all locked byte ranges in a file are unlocked.

Syntax

• C#
• VB.NET

public event OnAfterUnlockAllHandler OnAfterUnlockAll;

public delegate void OnAfterUnlockAllHandler(object sender, CbfilterAfterUnlockAllEventArgs e);

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

Public Event OnAfterUnlockAll As OnAfterUnlockAllHandler

Public Delegate Sub OnAfterUnlockAllHandler(sender As Object, e As CbfilterAfterUnlockAllEventArgs)

Public Class CbfilterAfterUnlockAllEventArgs Inherits EventArgs
  Public ReadOnly Property FileName As String
  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 all locked byte ranges in the file specified by FileName are unlocked.

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

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.