Chillout Lounge

Should I say this was quite a eventful year! I don’t know… !!

But,

A Year Where I’ve met so many new faces across the world, from the sweetest of all to the scariest of all to the charismatic of all…

A Year filled with travel, almost every weekend or alternate I was traveling…

A Year where I’ve made more number of flop shows and more flunks…

A Year filled with new experiences, some of which, I Didn’t know how to play…

Some of which, I Never wanted to repeat, if it repeats, Now I Know How to play the game!

A Year which changed perceptions towards life…

A Year Where I learned Amateur Photography…

[I've compiled a list of photos at http://photos.logukrishnan.net/Shots2005 ]

.

.

.

Welcome 2006…

Whoever, tries the FileSystemWatcher Class for first time, immedietly starts complaining about multiple event notifications and after a brief moment complains, that .NET is buggy and concludes that as a bug. Had heard this many times, and again recently came up with this issue…

Actually, the real root cause of this problem is the File System, NTFS. for e.g.: when a file modification operation occurs NTFS gives out 2 notifications,

Notification 1 : for Data Stream
Notification 2 : for Metadata

Hence 2 Notifications… Poor FSW Class, just handles this and does it’s job properly. Only possible way is to ignore the 2nd Notification.

else, we can use WMI and specify the polling interval, which should read something like the below,
“SELECT * FROM __InstanceModificationEvent WITHIN 10 …..”

Absolutely, nothing wrong in .NET…

New Blog… New Perceptions… New Thoughts…