filesystemwatcher

问题 I am using FileSystemWatcher to monitor a folder that will be used to do some file renaming. The only thing that will be copied will be folders containing files. There will not be single files put into the monitored folder. This is the code for setting up the FileSystemWatcher watcher.Path = path; watcher.NotifyFilter = NotifyFilters.DirectoryName | NotifyFilters.FileName; watcher.IncludeSubdirectories = true; watcher.Filter = "*.*"; watcher.Created += new FileSystemEventHandler(watcher

问题 It seems like , FileSystemWatcher triggers events more than once. Here is my settings ; watcher = new FileSystemWatcher(); watcher.Path = @"D:\testSpace"; watcher.InternalBufferSize = 1024*64; watcher.Deleted += Triggered; watcher.Changed += Triggered; watcher.Created += Triggered; watcher.Error += ErrorOccured; watcher.NotifyFilter = NotifyFilters.LastWrite; watcher.IncludeSubdirectories = true; watcher.EnableRaisingEvents = true; If you change a document , Document changed event triggered

问题 I am trying to run a file watcher over some server path using windows service. I am using my windows login credential to run the service, and am able to access this "someServerPath" from my login. But when I do that from the FileSystemWatcher it throws: The directory name \someServerPath is invalid" exception. var fileWatcher = new FileSystemWatcher(GetServerPath()) { NotifyFilter=(NotifyFilters.LastWrite|NotifyFilters.FileName), EnableRaisingEvents=true, IncludeSubdirectories=true }; public

问题 I have a FileSystemWatcher object in a Windows service. I wrote it in a console application using that app as a stub for my component. My component instantiates the FileSystemWatcher and sets up to watch a mapped drive. This works great for me from both the test stub Console App and the Deployable Windows Service. I also have the onError event hooked up with log4net logging a FATAL level error: public FileSystemWatcher CreateFileWatcher() { FileSystemWatcher watcher = new FileSystemWatcher();

问题 I want to build an app that needs to monitor the opening of the files but I don't find any way to can do it. With FileSystemWatcher there is no option to can monitor the opening of the files. Just the created, removed and modified ones. So I wonder if there is any functionality implemented in the advanced searches that could give me the infomration of the files opened after a concrete date. (At least in Mac it's possible but I am not sure if Windows has implemented this) Other solution would

问题 I've written a Windows Service (using Visual Studio 2010 Premium, C#, .NET 4) to monitor a folder. All it does is detect when a change is made in the folder (a file/folder added, something deleted, etc) and writes the detections to a text file. Not an Event Log, just a normal .txt file. Now, it installs fine (I presume), and it shows up in Computer Management and allows me to run it. It supposed to write "Monitoring started" to the file - but it doesn't. Then, when I try to stop the service

问题 I have a .csv file that is frequently updated (about 20 to 30 times per minute). I want to insert the newly added lines to a database as soon as they are written to the file. The FileSystemWatcher class listens to the file system change notifications and can raise an event whenever there is a change in a specified file. The problem is that the FileSystemWatcher cannot determine exactly which lines were added or removed (as far as I know). One way to read those lines is to save and compare the

问题 I want to monitor a folder and move files that match certain criteria, so I'm trying to use the FileSystemWatcher. I have a function that will be called with each new file: function ProcessFile() { param ([string]$filename) Write-Host "Processing file '$filename' to $destination" } And then I set up a FSW: Write-Host "Watching $source for new files..." $fsw = New-Object IO.FileSystemWatcher $source, $filter -Property @{IncludeSubdirectories = $false; NotifyFilter = [IO.NotifyFilters]'FileName

问题 I have developed file queue system, where several Apps from different Windows machines watch the same mapped network drive for file changes and proceed files. To watch mapped drive for changes I use FileSystemWatcher (c# .NET 4.0) and everything works fine for ~one day after that FileSystemWatcher stops monitoring. I have tried to play with FileSystemWatcher.Error event to catch exceptions if any. Unfortunately Error event is not always fired . I do not find a way to solve the problem,

问题 I have a simple C# 4.0 Windows Forms form that make an instance of a FileSystemWatcher which watches a directory. When a file is added, the proper event fires, and I do some stuff in another directory. Then I make an instance of a child form. The child form hangs, and controls do not paint. I think this is because the FileSystemWatcher is on a different thread, even though it looks like I am launching from the main form. What is the proper way to call a child form from a FileSystemWatcher