FileWatcher check on startup?

[tshad]

Is there some way to have the fileWatcher to initially check the folder to
see if there is anything in it (based on the filters)?

If I reboot the machine, for example, and it starts up the service - I would
like it to look at the folder initially. The reason being that I may bring
the system down and at that point the files may be written to the target
directory. When I bring it back up again and the service starts, it won't
see that the files were added to the folder while it was down and will never
see those files.

Thanks,

Tom

[Michael D. Ober]

"tshad" <ts***@dslextreme.comwrote in message
news:um**************@TK2MSFTNGP05.phx.gbl...

Is there some way to have the fileWatcher to initially check the folder to
see if there is anything in it (based on the filters)?

If I reboot the machine, for example, and it starts up the service - I
would like it to look at the folder initially. The reason being that I
may bring the system down and at that point the files may be written to
the target directory. When I bring it back up again and the service
starts, it won't see that the files were added to the folder while it was
down and will never see those files.

Thanks,

Tom

Immediately after setting up the file watcher, do a manual check via
File.Exists() or Directory.GetFiles() and handle anything you find at that
point.

Mike.

[Nicholas Paldino [.NET/C# MVP]]

Tom,

No, there isn't, but that doesn't mean that you can't scan the folder
yourself before you start the file watcher. Because you might run into a
situation where a file might be changed while the file watcher operates, you
might want to block the file watchers events from executing before you are
done scanning the directory initially.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"tshad" <ts***@dslextreme.comwrote in message
news:um**************@TK2MSFTNGP05.phx.gbl...

Is there some way to have the fileWatcher to initially check the folder to
see if there is anything in it (based on the filters)?

If I reboot the machine, for example, and it starts up the service - I
would like it to look at the folder initially. The reason being that I
may bring the system down and at that point the files may be written to
the target directory. When I bring it back up again and the service
starts, it won't see that the files were added to the folder while it was
down and will never see those files.

Thanks,

Tom

[tshad]

"Michael D. Ober" <obermd.@.alum.mit.edu.nospam.wrote in message
news:13*************@corp.supernews.com...

"tshad" <ts***@dslextreme.comwrote in message
news:um**************@TK2MSFTNGP05.phx.gbl...

>Is there some way to have the fileWatcher to initially check the folder
to see if there is anything in it (based on the filters)?

If I reboot the machine, for example, and it starts up the service - I
would like it to look at the folder initially. The reason being that I
may bring the system down and at that point the files may be written to
the target directory. When I bring it back up again and the service
starts, it won't see that the files were added to the folder while it was
down and will never see those files.

Thanks,

Tom

Immediately after setting up the file watcher, do a manual check via
File.Exists() or Directory.GetFiles() and handle anything you find at that
point.

I did Directory.GetFiles() and it worked fine.

Unfortunately, it doesn't seem to allow multiple filters, so I just did it 3
times as I needed to see files that started with "IN*", "GL*" and "TX*"
only.

Thanks,

Tom

>
Mike.