File system watcher created

Learn more. Asked 12 years, 1 month ago. Active 2 months ago. Viewed k times. Improve this question. SteveC It is a workaround, but it should be judged by the quality of the workaround. Keeping track of the changes works perfectly, and it's simple. OP is asking for a way to suppress duplicate events, and that's what the responses below give. I recently opended this issue github.

I have created a class that helps you get only one event. You can get the code from github. Add a comment. Active Oldest Votes. This is from the documentation of the class: You may notice in certain situations that a single creation event generates multiple Created events that are handled by your component. Improve this answer. David Brabant David Brabant I tried that and it worked if I modified one file at a time but if I modified two files at a time like copy 1.

It's been a couple months but I think what I ended up doing is having the event call a method that puts business logic inside of a lock statement. That way if I get extra events they queue up until it's their turn and there's nothing for them to do since the previous iteration took care of everything. This appears to fix the issue, but it does not. If another process is making changes you might lose them, the reason it appears to work is because the IO of the other process is async, and you disable monitoring till you are done your processing, thus creating a race condition with other events that might be of interest.

That is why ChristopherPainter observed his issue. Show 4 more comments. Shiva BaBu BaBu 1, 2 2 gold badges 16 16 silver badges 27 27 bronze badges. I like that solution, but I've used Rx to do the "right" thing change "Rename" to the name of the event you're interested in : Observable. Subscribe onNext ; — Kjellski. Am i missing something? I don't understand how this will work. From what Ive seen the events fire simultaneously so if they both enter the above event at the same time they will both start running before lastRead is set.

As DateTime only has millisecond resolution, this method works even if you replace File. Depending on your situation, you may also use the a. FullName in a global variable to detect duplicate events. Doesn't work as Asheh explained. This will work: if lastWriteTime. Ticks - lastRead. Show 5 more comments.

Here is my solution which helped me to stop the event being raised twice: watcher. FileName NotifyFilters. Shadow Wizard Is Vaccinated V3 Deepashri Deepashri 5 5 silver badges 11 11 bronze badges. Also, in Notepad, I created a file with four characters: abcd in it. I then opened a new instance of Notepad and entered the same four characters. I chose File Save As and chose the same file. The file is identical and the size and filename do not change, since the file has the same four letters, so this doesn't fire.

It's possible that a genuine change could be made which doesn't alter the size of the file, therefore this technique would fail in that situation. I would guess it is a fairly common case where you know that any meaningful change will modify the file size for example, my case was appending to a log file. While anyone who uses this solution should be aware of and document that assumption, this was exactly what I needed. GrandOpener: This is not always true. In my case I'm watching files where its content consists of just one character which is either 0 or 1.

GetLastWriteTime e. ContainsKey path fileWriteTime[path]. Ikon Ikon 8 8 silver badges 14 14 bronze badges. I assume you empty the hashtable periodically. This would be accurate to the second but if the period between the two changes is long enough to pass a second it will fail.

Moreover if you want more accuracy you could use ToString "o" but be prepared for more failures. Don't compare strings, use DateTime. Equals — Phillip Kamikaze. No, don't. They're not equal. In the case of my current project, they're about a millisecond apart. I use newtime-oldtime. Menelaos Vergis Menelaos Vergis 3, 3 3 gold badges 27 27 silver badges 39 39 bronze badges.

This seems to fail when an event is raised on a directory. I got it to work by wrapping a directory check before opening the file — Sam. Despite the typo in the example, this seems to be a viable solution for me. I still have to run some tests to find the value that fits best. I'd like someone to fork this and make it a NuGet package. Thanks : It solved my issue..

Hope the created and copied events will work properly with a single watcher to solve this problem well.

Worked for my app. Thanks a bunch — AlanC. Contains e. Add e. Remove e. Add your solution here. OK Paste as. Treat my content as plain text, not as HTML.

Existing Members Sign in to your account. This email is in use. Do you need your password? Submit your solution! When answering a question please: Read the question carefully. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.

If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.

Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question. Let's work to help developers, not make them feel stupid. For example, you create two instances of FileSystemWatcher. Unlike copying, moving a file or directory would raise two events.

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. Likewise, some applications for example, antivirus software might cause additional file system events that are detected by FileSystemWatcher.

The order in which the Created event is raised in relation to the other FileSystemWatcher events may change when the SynchronizingObject property is not null. The OnCreated event is raised as soon as a file is created. Occurs when the component is disposed by a call to the Dispose method.

Occurs when the instance of FileSystemWatcher is unable to continue monitoring changes or when the internal buffer overflows. Occurs when a file or directory in the specified Path is renamed. Skip to main content. This browser is no longer supported.

Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Namespace: System. IO Assembly: System. ISupportInitialize IDisposable. In this article. Changed , Created , Deleted. FileSystemWatcher String. FileSystemWatcher String, String. Gets a value indicating whether the component can raise an event.

Inherited from Component. Gets or sets the filter string used to determine what files are monitored in a directory. CreateObjRef Type. Inherited from MarshalByRefObject. Dispose Boolean. Equals Object. Determines whether the specified object is equal to the current object. Inherited from Object.

Serves as the default hash function. GetService Type. Obtains a lifetime service object to control the lifetime policy for this instance.