You use the File Watcher application to monitor a file system and react when changes to the directories or files it contains occur. This makes it possible for you to quickly and easily launch business processes when certain files or directories are created, modified, or deleted. For example, suppose you and a group of coworkers are collaborating on a document that is stored on a shared directory on your server. Using File Watcher, you can program your application to watch for changes to the contents of that shared directory. When a change is detected, the component can run procedures that notify each of the group members via e-mail.

Note File Watcher is designed to watch for changes within a directory, not to changes to the root directory's attributes themselves. For example, if you are watching a directory called c:\ftp, the component will monitor changes within the directory but not changes to the root directory itself.

You can configure File Watcher to watch either an entire directory and its contents or a specific file or set of files within a given directory. The File Watcher raises an event whenever a file or subdirectory within the specified root directory is created, deleted, renamed, or changed in some other way. The types of changes that the component monitors include changes in the file's or subdirectory's attributes, size, last write time, last access time, and security settings.

When changes occur within a root directory or to a file your application is monitoring, one or more events are raised, File Watcher gives you access to the following events:

Created — raised whenever a directory or file is created.
Deleted — raised whenever a directory or file is deleted.
Renamed — raised whenever the name of a directory or file is changed.
Changed — raised whenever changes are made to the size, system attributes, last write time, last access time, or security permissions of a directory or file.

Note Although some common occurrences, such as copying or moving a file, do not correspond directly to an event, these occurrences do cause events to be raised. When you copy a file, the system raises a Created event in the directory to which the file was copied but does not raise any events in the original directory. When you move a file, the server raises two events: a Deleted event in the source directory, followed by a Created event in the target directory.

Each change to a file in a directory raises a separate event. If a user makes multiple changes to a single file, the application raises a separate event for each change. For example, if you are watching a directory that contains five files and the security permissions for all of the files suddenly change, you will receive five Changed events. If the user renames and assigns new security permissions to each of those files, you will receive 10 event notifications — a Changed event and a Renamed event for each of the five files.

Buy It

Requirements	If you have	If you have
Microsoft .NET Framework	1.1	2.0
need Service Pack	KB867460	none
need Hotfix	KB886903	none

Supporting Documentation