C# manual lock/unlock

by

The lock keyword is just syntactic sugar for Monitor.Enter and Monitor.Exit:

Monitor.Enter(o);
try
{
    //put your code here
}
finally
{
    Monitor.Exit(o);
}

is the same as

lock(o)
{
    //put your code here
}

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. Throw a NullReferenceException while calling the set_item method of a Dictionary object in a multi-threading scenario
  15. Why does the lock object have to be static?
  16. When is ReaderWriterLockSlim better than a simple lock?
  17. Cross-Process Locking in C#
  18. Why is it a bad practice to lock the object we are going to change?
  19. Guidelines of when to use locking
  20. What’s wrong with using Thread.Abort()
  21. Change WPF controls from a non-main thread using Dispatcher.Invoke
  22. How to kill a thread instantly in C#?
  23. Updating an ObservableCollection in a separate thread
  24. How to catch exceptions from a ThreadPool.QueueUserWorkItem?
  25. WPF UI multitasking
  26. What is the difference between ManualResetEvent and AutoResetEvent in .NET?
  27. Lock (Monitor) internal implementation in .NET
  28. .NET 4.0 and the dreaded OnUserPreferenceChanged Hang
  29. SynchronizationLockException on Monitor.Exit when using await
  30. How to handle Task.Run Exception

Leave a Comment