I don’t think FSW supports monitoring multiple folders, so just instantiate one per folder you want to monitor. You can point the event handlers at the same methods, though, which should end up working like I think you want.
You seem to be creating the FileSystemWatcher as a local variable in the setup method. This will of course go out of scope at the end of the method and may well be getting tidied up at that point, thus removing the watches. Try creating the FSW at a point where it will be persisted … Read more
Here’s a simplified and corrected version of fletcher’s solution: namespace Watcher { class Program { private const string Directory = @”C:\Temp”; private static FileSystemWatcher _fileWatcher; private static FileSystemWatcher _dirWatcher; static void Main(string[] args) { _fileWatcher = new FileSystemWatcher(Directory); _fileWatcher.IncludeSubdirectories = true; _fileWatcher.NotifyFilter = NotifyFilters.FileName; _fileWatcher.EnableRaisingEvents = true; _fileWatcher.Deleted += WatcherActivity; _dirWatcher = new FileSystemWatcher(Directory); _dirWatcher.IncludeSubdirectories … Read more
You need to get the parent directory from the WatchKey to resolve the full path WatchKey key; WatchEvent<Path> event; Path dir = (Path)key.watchable(); Path fullPath = dir.resolve(event.context()); This piece of code reads like it needs accompanying documentation to be grasped, it makes little sense on its own. What were their intentions with this particular API … Read more
A typical problem of this approach is that the file is still being copied while the event is triggered. Obviously, you will get an exception because the file is locked during copying. An exception is especially likely on large files. As a workaround you could first copy the file and then rename it and listen … Read more
The problem was the notify filters. The program was trying to open a file that was still copying. I removed all of the notify filters except for LastWrite. private void watch() { FileSystemWatcher watcher = new FileSystemWatcher(); watcher.Path = path; watcher.NotifyFilter = NotifyFilters.LastWrite; watcher.Filter = “*.*”; watcher.Changed += new FileSystemEventHandler(OnChanged); watcher.EnableRaisingEvents = true; }
From a server load point of view, using the IO.FileSystemWatcher for remote change notifications in the scenario you describe is probably the most efficient method possible. It uses the FindFirstChangeNotification and ReadDirectoryChangesW Win32 API functions internally, which in turn communicate with the network redirector in an optimized way (assuming standard Windows networking: if a third-party … Read more
Your error is setting the Path property with a full filename watcher.Path = Path.GetDirectoryName(filePath1); watcher.Filter = Path.GetFileName(filePath1); should work. Not related to your proper question, but, of course, to enable the FileSystemWatcher’s functionality, it is imperative to set the EnableRaisingEvents property to true.
You can’t do that. The Filter property only supports one filter at a time. From the documentation: Use of multiple filters such as *.txt|*.doc is not supported. You need to create a FileSystemWatcher for each file type. You can then bind them all to the same set of FileSystemEventHandler: string[] filters = { “*.txt”, “*.doc”, … Read more
I’ve done something similar using the inotifywait tool: #!/bin/bash while true; do inotifywait -e modify,create,delete -r /path/to/your/dir && \ <some command to execute when a file event is recorded> done This will setup recursive directory watches on the entire tree and allow you to execute a command when something changes. If you just want to … Read more