I've recently upgraded to ReaderWriterLockSlim for an app i'm writing from the much fatter ReaderWriterLock and apparently more prone to deadlock situations.
I see for the new slim lock, there are a number of count properties which can show current read counts, waiting write count, waiting read count.
Is their is standard usage scenario for using these properties. The app i'm developing makes heavy use of locking and threading, and it would be interesting to do some profiling of how the threads/locking is performing.
Would it just be a case, I could have a thread firing of every say 0.5,1,2 second, in a wee block of code outside the main logic, that would dump these values to a log.
Bob.