When I first worked with the FileSystemWatcher class, I ended up experimenting with combinations of
NotifyFilters and event handlers to get the desired result; it is not immediately clear, which changes to files and folders, trigger which events.
The job can only get harder when also up against known issues (just search on stackoverflow.com) with events firing twice.
Here, I hope to provide simple guidance on using the
NotifyFilter enumeration for those just starting out with
What is a NotifyFilter?
These filters determine what you are watching and thus, which events can be triggered.
They can also be helpful in limiting the number of events trigger in some scenarios where complex file operations, or applications like antivirus software cause additional events to be triggered (see above) although you can’t have 100% confidence without some additional defensive coding.
Note that the default values for the
NotifyFilter property are
So, What Filters Can Result in a Changed Event Being Triggered?
Which Filters Can Result in a Renamed Event Being Triggered?
Which Filters Can Result in a Created Event Being Triggered?
And Which Filters Can Result in a Deleted Event Being Triggered?
In case you missed it in the MSDN documentation, you can combine more than one
NotifyFilters member by using the bitwise OR operator like so:
...NotifyFilter = NotifyFilters.LastAccess | NotifyFilters.LastWrite
| NotifyFilters.FileName | NotifyFilters.DirectoryName;
I Get Two Events When I Create a New File… What’s With That?
Most guides to
FileWatcher tend to lead you towards the
Changed event. However, using this often leads to multiple events, which is not desirable. Try out the code in this gist to see the two-event behaviour (just copy a file into c:\temp when it’s running). Then try out the code in this other gist, demonstrating how you can use
NotifyFilters.FileName to get a single event from a new file in a folder.
A Bit More….Where are the Events for Copying and Moving?
Copied files will trigger
Created events in the destination folder, so use
The same applies for moved files but you can also watch the source folder for
Deleted events (still using the same
The above works for copied and moved folders (using instead,
NotifyFilters.DirectoryName), although more code is required to trigger events for any files inside the folder. Seehttps://msdn.microsoft.com/en-us/library/system.io.filesystemwatcher(v=vs.110).aspx.
Appendix A – Table Detailing NotifyFilters Enumeration from MSDN
|Attributes ||The attributes of the file or folder |
|The time the file or folder was created |
|The name of the directory |
|The name of the file |
|The date the file or folder was last opened |
|The date the file or folder last had anything written to it |
|The security settings of the file or folder |
|The size of the file or folder |
Appendix B – Table of Events You’ll Be Interested In If You’ve Landed Here
|Occurs when a file or directory in the specified Path is changed. |
|Occurs when a file or directory in the specified Path is created. |
|Occurs when a file or directory in the specified Path is deleted. |
|Occurs when a file or directory in the specified Path is renamed. |