>From what I have read. I think it was true. FileSystemWatcher is used to prevent polling checking time stamp and reduce HDD activity. It is use kernel level and can raise an asynchronous event.
However you may need to alert issues regarding FileSystemWatcher. One thing I know, don't let the event buffer overflow and missed the event. So limit your IncludeSubDirectories and NotifyFilter. Also know how the copy-paste or cut-paste being triggered, its stated in the msdn doc. http://msdn.microsoft.com/en-us/library/system.io.filesystemwatcher.aspx http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/4465cafb-f4ed-434f-89d8-c85ced6ffaa8 http://articles.techrepublic.com.com/5100-10878_11-6165137.html On Apr 20, 4:40 pm, cipherwar <[email protected]> wrote: > Hello, > > I read a lot about the .NET FileSystemWatcher. > E.g.http://www.codeproject.com/KB/vb/AdvancedFileSystemWatcher.aspxhttp://vbnotebookfor.net/2007/10/01/introduction-to-filesystemwatcher/ > > Can anybody tell me how much resources a FileSystemWatcher in waiting > state consumes? > > I would exspect, as there seems not to be an active polling of a > special directory, but only a kind of waiting for getting informed > about an Event, there is nearly no rescource consuming on CPU or > memory... > > Am i right? > > Cipherwar
