![filewatcher dmedia filewatcher dmedia](https://freelancelogodesign.com/48hourslogo_data/2015/05/16/2015051621274016534.png)
It will not accept compressed (.zip) folder archives. This option is available in any folder type and reloads an unzipped folder archive.
![filewatcher dmedia filewatcher dmedia](https://thumbs.dreamstime.com/b/folder-icon-magnifier-27938172.jpg)
You may notice in certain situations that a single creation event generates multiple Created events that are handled by your component.
![filewatcher dmedia filewatcher dmedia](https://thumbs.dreamstime.com/b/file-search-line-vector-icon-elements-mobile-concept-web-apps-thin-icons-website-design-development-app-premium-folder-104427007.jpg)
I came across the following in the MSDN documentation’s Troubleshooting FileSystemWatcher Components Multiple Created Events Generated for a Single Action
#FILEWATCHER DMEDIA MANUAL#
While doing some manual testing of my initial implementation it was very obvious that the FileSystemWatcher was firing multiple events whenever I made a change to a file or copied a file into the directory being monitored. When a change occurs, the application needs to read the file and immediately perform some operation based on the contents of the file. My requirements were to monitor a directory for new files or changes to existing files. NET framework provides a FileSystemWatcher class that can be used to monitor the file system for changes.