Guidelines of when to use locking

by

The best guide for locking and threading I found, is this page (this is the text I consult when working with locking and threading):

http://www.albahari.com/threading/

You want the paragraph “Locking and Thread Safety”, but read the rest as well, it is very well written.

More Related Contents:

  1. Why is lock(this) {…} bad?
  2. Volatile vs. Interlocked vs. lock
  3. Concurrent HashSet in .NET Framework?
  4. Asynchronous locking based on a key
  5. Re-entrant locks in C#
  6. Is Task.Factory.StartNew() guaranteed to use another thread than the calling thread?
  7. Is it OK to use a string as a lock object?
  8. Does a locked object stay locked if an exception occurs inside it?
  9. How expensive is the lock statement?
  10. Monitor vs lock
  11. lock keyword in C#
  12. What are the differences between various threading synchronization options in C#?
  13. Do I need to lock or mark as volatile when accessing a simple boolean flag in C#?
  14. C# manual lock/unlock
  15. Throw a NullReferenceException while calling the set_item method of a Dictionary object in a multi-threading scenario
  16. Why does the lock object have to be static?
  17. When is ReaderWriterLockSlim better than a simple lock?
  18. Cross-Process Locking in C#
  19. Why is it a bad practice to lock the object we are going to change?
  20. C# Thread Termination and Thread.Abort()
  21. C#: Waiting for all threads to complete
  22. Set timeout to an operation
  23. Workaround for the WaitHandle.WaitAll 64 handle limit?
  24. Getting Cross-thread operation not valid [duplicate]
  25. Waiting for all threads to complete, with a timeout
  26. Dispatcher Invoke(…) vs BeginInvoke(…) confusion
  27. Is C# += thread safe?
  28. C# multi-threading: Acquire read lock necessary?
  29. Write to a file from multiple threads asynchronously c#
  30. .NET Core equivalent to Thread.Abort

Leave a Comment