
There are times when a directory needs watched. For reasons of its own, a program may need to know when a file is deleted, updated or renamed. If .NET is involved, this is a trivial task. Create an instance of the FileSystemWatcher; set some properties, and the task is completed. If a non .NET solution is required (and regardless of the hype, some people haven't embraced .NET in all of its glory.), the ReadDirectoryChangesW function must be used, however the documentation for ReadDirectoryChangesW is sketchy at best.
>
There are times when a directory needs watched. For reasons of its own, a program may need to know when a file is deleted, updated or renamed. If .NET is involved, this is a trivial task
>
>
There are hell of a lot of things .NET isn't good for and this is one of them.
Who in their right mind is going to let some crap running under .NET delete, update or rename any fricking files without their permission if they can help it?
And if they are going to give their permission why bother
running a .NET app to begin with?
......
I think that you should understand what you are reading before you post a comment. The article is about monitoring file system actions, not performing them.