|
using System;
using System.Diagnostics.CodeAnalysis;
using System.Threading;
using Pfz.Threading;
using Pfz.Threading.Disposers;
namespace Pfz.Extensions.MonitorLockExtensions
{
/// <summary>
/// Adds methods to lock any object using Monitor methods easily and
/// always with time-out, so you can avoid dead-locks.
/// See PfzLockConfiguration class if you want to log dead-locks.
/// </summary>
public static class PfzMonitorLockExtensions
{
#region LockWithTimeout - Disposable
/// <summary>
/// Tries to acquire a lock on the given object, using the default lock-timeout.
/// In case of failure, it logs the error, but does not generates an exception. Instead, it returns
/// null.
/// </summary>
/// <typeparam name="T">The type of class to lock.</typeparam>
/// <param name="item">The item to lock.</param>
/// <returns>A disposable object, so you can release the lock, or null if the lock was not acquired.</returns>
public static MonitorLockDisposer TryLockWithTimeout<T>(this T item)
where
T: class
{
return TryLockWithTimeout(item, LockConfiguration.DefaultLockTimeout);
}
/// <summary>
/// Tries to acquire a lock on the given object, using the given time-out.
/// In case of failure, it logs the error, but does not generates an exception. Instead, it returns
/// null.
/// </summary>
/// <typeparam name="T">The type of class to lock.</typeparam>
/// <param name="item">The item to lock.</param>
/// <param name="timeoutInMilliseconds">The timeout value while trying to acquire the lock.</param>
/// <returns>A disposable object, so you can release the lock, or null if the lock was not acquired.</returns>
[SuppressMessage("Microsoft.Reliability", "CA2000:Dispose objects before losing scope")]
public static MonitorLockDisposer TryLockWithTimeout<T>(this T item, int timeoutInMilliseconds)
{
MonitorLockDisposer result = new MonitorLockDisposer(item, timeoutInMilliseconds);
if (result._lockTaken)
return result;
return null;
}
#endregion
#region Lock
/// <summary>
/// Locks the actual object and returns a Disposable object.
/// You can, then, dispose it before the end of the block is
/// achieved with using, but without calling excessive exits.
/// This is not abort-safe.
/// </summary>
[SuppressMessage("Microsoft.Reliability", "CA2000:Dispose objects before losing scope")]
public static MonitorLockDisposer Lock(this object item)
{
MonitorLockDisposer result = new MonitorLockDisposer(item, Timeout.Infinite);
return result;
}
#endregion
}
}
|
By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.
If a file you wish to view isn't highlighted, and is a text file (not binary), please
let us know and we'll add colourisation support for it.
I started to program computers when I was 11 years old, as a hobbyist, programming in AMOS Basic and Blitz Basic for Amiga.
At 12 I had my first try with assembler, but it was too difficult at the time. Then, in the same year, I learned C and, after learning C, I was finally able to learn assembler (for Motorola 680x0).
Not sure, but probably between 12 and 13, I started to learn C++. I always programmed "in an object oriented way", but using function pointers instead of virtual methods.
At 15 I started to learn Pascal at school and to use Delphi. At 16 I started my first internship (using Delphi). At 18 I started to work professionally using C++ and since then I've developed my programming skills as a professional developer in C++ and C#, generally creating libraries that help other developers do their work easier, faster and with less errors.
Want more info or simply want to contact me?
Take a look at:
http://paulozemek.azurewebsites.net/
Or e-mail me at: paulozemek@outlook.com
Codeproject MVP 2012, 2015 & 2016
Microsoft MVP 2013-2014 (in October 2014 I started working at Microsoft, so I can't be a Microsoft MVP anymore).