filesystemwatcher

I have the following code which creates a temporary folder and uses a FileSystemWatcher to poll for files added to the folder on the Location property, and add them to a list: Scratchdisk.cs on Pastebin . The idea is to create a Scratchdisk object, and have FFmpeg extract video frames into it, the FileSystemWatcher builds a list of these files as FFmpeg creates them, and the list is presented as a DependencyObject that my UI binds to. I'm binding to the Scratchdisk object like so: <ItemsControl ItemsSource="{Binding Source=ThumbnailScratchdisk, Path=FileList}"> ... </ItemsControl> On actually

I"m looking for something (Win API calls or whatever) to notify me when a file becomes available for editing (i.e. no longer in use). Should I set up a timer to check the files on some interval or is there a good way to set up a watch on the file? FileSystemWatcher doesn't help, nor does the Win32 FindFirstChangeNotification: they won't tell you when someone releases a file handle. Your best way is to periodically attempt to open the file with the access you want, handling any errors. Even if you were notified that a file was available, that won't guarantee that it will still be available when

Ok, so I learnt from How to check if a open file has been updated that I should use a FileSystemWatcher to watch for changes to files. Then now, the question is if I must keep track of many files, do I create 1 watcher for each file? Also, I must somehow dispose of the watcher once the file is closed. Is having a Dictionary<string, FileSystemWatcher> storing the filepath and the FileSystemWatcher the way to go? as I open more files, I add more watcher and as I close, dispose of the watchers appropriately. Will having too many watchers be a bad thing? UPDATE I just did protected void

I setup a FsWatcher on a local filesystem directory. I only want to know when files are added to the directory so they can be moved to another filesystem. I seem to be able to detect when the first file is in, but actually I want to know when all files from a given copy operation are done. If I used Windows Explorer to copy files from one directory to another, Explorer would tell me that there are n seconds left in the transfer, so while there is some activity for the begin-transfer and end-transfer for each file, it appears that there is something for the begin-transfer and end-transfer for

I have been following the guidance here FileSystemWatcher Changed event is raised twice . However I have a list of files that I'm watching so if I delete 20 files together the event is called 20 times. This is expected and works fine. How can I only have an event fired once for 20 "simultaneous" file changes (i.e How can I ignore all other file changes until the code in the first instance of Onchanged below has completed. Right now Onchanged is called 20 times.) ? private void Main_Load(object sender, EventArgs e) { public static List<FileSystemWatcher> watchers = new List<FileSystemWatcher>()

[Using C# and Windows as platform] I have a camera that writes JPG files to a local folder in my PC. I want to load each file the camera drops, so I have a FileSystemWatcher that notifies me whenever a new picture is created, but the camera locks the file while it's being written , so if I try to load it just after being notified of its creation, I get an exception saying that the file is locked . Currently, I have a while loop (with a Thread.Sleep) that retries to load the image every 0.2 seconds, but it feels a bit dirty. Is there a more elegant way to wait until the lock has been released,

I have a FileSystemWatcher that I would like to fire an OnCreated event for every folder copied into the watched directory . Several folders will be copied into this watched directory at once, manually. Currently it is only firing the event for the first folder copied. So if I'm watching folder X and select folders A,B,C in windows explorer and copy them into X, OnCreated is fired for A but not B or C. This is my code that I'm using to set up the FileSystemWatcher : watcher = new System.IO.FileSystemWatcher(watchPath); watcher.InternalBufferSize = 32768; watcher.IncludeSubdirectories = true;