this post is to clear how to use WriteLock and ReadLock to make sure critical resources have been visited properly.<\/p>\n
Take the following code for example in “public abstract class ResolverBase \/\/The lock for the singleton. when it disposed by calling IDisposable.Dispose(), invoking “_rwLock.ExitWriteLock();” to exit WriteLock.<\/p>\n “new ReadLock(ResolversLock)” is called, “ResolversLock” will be referenced by _rwLock. ReadLock constructor will enter lock automatically and exit readlock when disposed.<\/p>\n","protected":false},"excerpt":{"rendered":" this post is to clear how to use WriteLock and ReadLock to make sure critical resources have been visited properly. Take the following code for example in “public abstract class ResolverBase : ResolverBase where TResolver : ResolverBase”. public static TResolver … Continue reading \r\npublic static TResolver Current\r\n{\r\n get\r\n {\r\n using (new ReadLock(ResolversLock))\r\n {\r\n if (_resolver == null)\r\n throw new InvalidOperationException(string.Format(\"Current has not been initialized on {0}. You must initialize Current before trying to read it.\",\r\n typeof(TResolver).FullName));\r\n return _resolver;\r\n }\r\n }\r\n\r\n set\r\n {\r\n using (Resolution.Configuration)\r\n using (new WriteLock(ResolversLock))\r\n {\r\n if (value == null)\r\n throw new ArgumentNullException(\"value\");\r\n if (_resolver != null)\r\n throw new InvalidOperationException(string.Format(\"Current has already been initialized on {0}. It is not possible to re-initialize Current once it has been initialized.\",\r\n typeof(TResolver).FullName));\r\n _resolver = value;\r\n }\r\n }\r\n}\r\n<\/pre>\n
\nstatic readonly ReaderWriterLockSlim ResolversLock = new ReaderWriterLockSlim();
\n“new WriteLock(ResolversLock)” is called, “ResolversLock” will be referenced by _rwLock. WriteLock constructor will enter lock automatically by “_rwLock.EnterWriteLock();”<\/p>\n