When I ran into this problem, the best solution I came up with was to continually try to get an exclusive lock on the file; while the file is being written, the locking attempt will fail, essentially the method in this answer. Once the file isn’t being written to any more, the lock will succeed. … Read more
Solution found on stackoverflow and modified it a bit. static bool IsFileLocked(FileInfo file) { FileStream stream = null; try { stream = file.Open(FileMode.Open, FileAccess.ReadWrite, FileShare.None); } catch (IOException) { //the file is unavailable because it is: //still being written to //or being processed by another thread //or does not exist (has already been processed) return … Read more
You don’t have to create a thread. The events will be called on a separate thread automatically.
FileSystemWatcher relies on underlying file system support, so any reliability issues with the file system will be visible as reliability issues with FileSystemWatcher. For example, if you are watching a network directory, then the network server’s reliability will affect FileSystemWatcher‘s reliability. For example, the server may crash and be restarted. You will not be notified … Read more
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
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
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
On Linux, you could be interested in pyinotify https://github.com/seb-m/pyinotify Other related libraries: http://people.gnome.org/~veillard/gamin/python.html Python FAM interface: http://python-fam.sourceforge.net/ http://gorakhargosh.github.com/watchdog/
According to the docs: Common file system operations might raise more than one event. For example, when a file is moved from one directory to another, several OnChanged and some OnCreated and OnDeleted events might be raised. Moving a file is a complex operation that consists of multiple simple operations, therefore raising multiple events. So … Read more
I just tried this: var _watcher = new FileSystemWatcher(); _watcher.Path = @”\\10.31.2.221\shared\”; _watcher.NotifyFilter = NotifyFilters.LastWrite | NotifyFilters.FileName; _watcher.Filter = “*.txt”; _watcher.Created += new FileSystemEventHandler((x, y) =>Console.WriteLine(“Created”)); _watcher.Error += new ErrorEventHandler( (x, y) =>Console.WriteLine(“Error”)); _watcher.EnableRaisingEvents = true; Console.ReadKey(); That works without problems, however i replicated your exception just when: The running user doesn’t have permissions to … Read more