PRJ_NOTIFY_TYPES Enumeration |
Types of notifications describing a change to the file or folder.
Maps to Windows' PRJ_NOTIFICATION enumeration..
Namespace: ShellBoost.Core.ProjFS
Assembly: ShellBoost.Core (in ShellBoost.Core.dll) Version: 1.8.3.0
SyntaxC#
[FlagsAttribute] public enum PRJ_NOTIFY_TYPES
Members| Member name | Value | Description | |
|---|---|---|---|
| PRJ_NOTIFY_NONE | 0 | No notification. | |
| PRJ_NOTIFY_SUPPRESS_NOTIFICATIONS | 1 | If received in a notification: this notification value is not sent. If specified on virtualization instance start: indicates that notifications should not be sent for the virtualization instance, or a specified subtree of the instance. If specified in response to a notification: indicates that notifications should not be sent for the specified file or folder until all handles to it are closed. | |
| PRJ_NOTIFY_FILE_OPENED | 2 | If received in a notification: indicates that a handle has been created to an existing file or folder, the provider can specify a new notification mask for this file or folder when responding to the notification. If specified on virtualization instance start: indicates that the provider should be notified when a handle is created to an existing file or folder. If specified in response to a notification: indicates that the provider should be notified if any further handles are created to the file or folder. | |
| PRJ_NOTIFY_NEW_FILE_CREATED | 4 | If received in a notification: a new file or folder has been created, the provider can specify a new notification mask for this file or folder when responding to the notification. If specified on virtualization instance start: the provider should be notified when a new file or folder is created. If specified in response to a notification: no effect. | |
| PRJ_NOTIFY_FILE_OVERWRITTEN | 8 | If received in a notification: an existing file has been overwritten or superceded, the provider can specify a new notification mask for this file or folder when responding to the notification. If specified on virtualization instance start: indicates that the provider should be notified when an existing when an existing file is overwritten or superceded. If specified in response to a notification: indicates that the provider should be notified when the file or folder is overwritten or superceded. | |
| PRJ_NOTIFY_PRE_DELETE | 16 | If received in a notification: a file or folder is about to be deleted. If the provider returns an error code from the callback, the delete will not take effect. If specified on virtualization instance start: indicates that the provider should be notified when a file or folder is about to be deleted. If specified in response to a notification: indicates that the provider should be notified when a file or folder is about to be deleted. | |
| PRJ_NOTIFY_PRE_RENAME | 32 | If received in a notification: a file or folder is about to be renamed. If the provider returns an error code from the callback, the rename will not take effect. If specified on virtualization instance start: indicates that the provider should be notified when a file or folder is about to be renamed. If specified in response to a notification: indicates that the provider should be notified when a file or folder is about to be renamed. | |
| PRJ_NOTIFY_PRE_SET_HARDLINK | 64 | If received in a notification: a hard link is about to be created for the file. If the provider returns an error code from the callback, the hard link operation will not take effect. If specified on virtualization instance start: indicates that the provider should be notified when a hard link is about to be created for a file. If specified in response to a notification: indicates that the provider should be notified when a hard link is about to be created for a file. | |
| PRJ_NOTIFY_FILE_RENAMED | 128 | If received in a notification: indicates that a file/folder has been renamed. The file/folder may have been moved into the virtualization instance. If specified on virtualization instance start: indicates that the provider should be notified that a file or folder has been renamed. If specified in response to a notification: indicates that the provider should be notified when a file or folder has been renamed. | |
| PRJ_NOTIFY_HARDLINK_CREATED | 256 | If received in a notification: indicates that a hard link has been created for the file. If specified on virtualization instance start: indicates that the provider should be notified that a hard link has been created for a file. If specified in response to a notification: indicates that the provider should be notified that a hard link has been created for the file. | |
| PRJ_NOTIFY_FILE_HANDLE_CLOSED_NO_MODIFICATION | 512 | If received in a notification: a handle has been closed on the file/folder, and the file’s content was not modified while the handle was open, and the file/folder was not deleted If specified on virtualization instance start: yhe provider should be notified when a handle is closed on a file/folder and the closing handle neither modified nor deleted it. If specified in response to a notification: yhe provider should be notified when handles are closed for the file/folder and there were no modifications or deletions associated with the closing handle. | |
| PRJ_NOTIFY_FILE_HANDLE_CLOSED_FILE_MODIFIED | 1024 | If received in a notification: a handle has been closed on the file, and that the file’s content was modified while the handle was open. If specified on virtualization instance start: the provider should be notified when a handle is closed on a file/folder and the closing handle was used to modify it. If specified in response to a notification: the provider should be notified when a handle is closed on the file/folder and the closing handle was used to modify it. | |
| PRJ_NOTIFY_FILE_HANDLE_CLOSED_FILE_DELETED | 2048 | If received in a notification: a handle has been closed on the file/folder, and that it was deleted as part of closing the handle. If specified on virtualization instance start: the provider should be notified when a handle is closed on a file/folder and it is deleted as part of closing the handle. If specified in response to a notification: the provider should be notified when a handle is closed on the file/folder and it is deleted as part of closing the handle. | |
| PRJ_NOTIFY_FILE_PRE_CONVERT_TO_FULL | 4096 | If received in a notification: the file is about to be expanded from a placeholder to a full file, i.e. its contents are likely to be modified. If the provider returns an error code from the callback, the file will not be expanded to a full file, and the I/O that triggered the conversion will fail. If there are multiple racing I/Os that would expand the same file, the provider will receive this notification value only once for the file. If specified on virtualization instance start: the provider should be notified when it is about to convert a placeholder to a full file. If specified in response to a notification: the provider should be notified when it is about to convert the placeholder to a full file, assuming it is a placeholder and not already a full file. | |
| PRJ_NOTIFY_USE_EXISTING_MASK | -1 | If received in a notification: this notification is not sent by the API. If specified on virtualization instance start: this value is not valid on virtualization instance start. If specified in response to a notification: continue to use the existing set of notifications for this file/folder. |
See Also