filesystemwatcher

I am about to implement the archetypal FileSystemWatcher solution. I have a directory to monitor for file creations, and the task of sucking up created files and inserting the into a DB. Roughly this will involve reading and processing 6 or 7, 80 char text files that appear at a rate of 150mS in bursts that occur every couple of seconds, and rarely a 2MB binary file will also have to be processed. This will most likely be a 24/7 process. From what I have read about the FileSystemWatcher object it is better to enqueue its events in one thread and then dequeue/process them in another thread. The

Something intrigues me and I don't find any resource on this. How can FileSystemWatcher know when a file on a computer "A" is created/removed/changed/renamed ? I thought that this worked with polling, (the observer polls the server to check update), but after verifying the network activity with Wireshark I saw that polling was not used. Does the SMB protocol use a observable/observer pattern ? In this case how the server can know when a client doesn't observe him anymore ? What is the consequence when the network falls during an observation and comes back right after? Using FileSystemWatcher

I have created a relatively simple windows app that watches a folder for files. When a new file is created into the folder the app (via FileSystemWatcher) will open the file and process the contents. Long story short, the contents are used with Selenium to automate a web page via IE11. This processing takes about 20 seconds per file. The problem is if more than one file is created into the folder at roughly the same time or when the app is processing a file, FileSystemWatcher onCreated does not see the next file. So when processing completes on the first file the app just stops. Meanwhile

Note: Running PowerShell v3 I've got a directory setup that is currently: \ftproot\001\converted \ftproot\001\inbound \ftproot\001\pdf \ftproot\002\converted \ftproot\002\inbound \ftproot\002\pdf \ftproot\xxx\converted \ftproot\xxx\inbound \ftproot\xxx\pdf Each FTP user is mapped to an inbound directory. The structure can be changed if this makes the solution easier \ftproot\converted\001 \ftproot\converted\002 \ftproot\converted\xxx \ftproot\inbound\001 \ftproot\inbound\002 \ftproot\inbound\xxx \ftproot\pdf\001 \ftproot\pdf\002 \ftproot\pdf\xxx I need to monitor each inbound directory for

Using FileSystemWatcher we can monitor the IO activity of a particular file system, but is there anyway to know that which one of the running processes is causing that IO? More specifically, suppose a running process viz. abc.exe is creating a file text.txt on drive D. We can monitor that a file named text.txt has been created in drive D using FileSystemWatcher, but can we determine programmatically that a process named abc.exe is creating that particular file in drive D? handle.exe from SysInternals is a command line tool that allow programmatic access to which program has a particular file

So far I know that FileSystemWatcher can look into a folder and if any of the files inside that folder is changed,modifies,.etc... then we can handle it. But I am not sure which filter and event I should use in my scenario: Watch for a Folder, If a file is added to that folder, do XYZ ... So In my scenario I don't care if an existing file is changed,etc..those should be ignored...only do XYZ if and only if a new file has been added to that Folder... Which event and filter do you recommended for this scenario? David Brabant Set up the watcher: FileSystemWatcher watcher = new FileSystemWatcher()