C# Programming
02-14-2010, 05:51 PM
I've looked and haven't found anything about this anywhere, so before I write an article about my solution, I thought I'd ask here.
The FileSystemWatcher supports one or more NotifyFilters when watching for changes to a folder/file. However, if you have more than one NotifyFilter specified, there is apparently no way (at least with a single FileSystemWatcher) to determine *exactly* what change occurred that caused the Changed event to be posted.
Am I correct, or am I just not seeing it?.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
The FileSystemWatcher supports one or more NotifyFilters when watching for changes to a folder/file. However, if you have more than one NotifyFilter specified, there is apparently no way (at least with a single FileSystemWatcher) to determine *exactly* what change occurred that caused the Changed event to be posted.
Am I correct, or am I just not seeing it?.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001