[
https://issues.apache.org/jira/browse/LOG4NET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851392#action_12851392
]
Piers Williams edited comment on LOG4NET-232 at 3/30/10 1:22 PM:
-----------------------------------------------------------------
Since ReaderWriterLockSlim is a .net 3.5 addition (in System.Core), building on
.net 3.5 is required to fix this issue
See https://issues.apache.org/jira/browse/LOG4NET-176
was (Author: piers7):
Since ReaderWriterLockSlim is a .net 3.5 addition (in System.Core),
building on .net 3.5 is required to fix this issue
> Use ReaderWriterLockSlim instead of ReaderWriterLock.
> -----------------------------------------------------
>
> Key: LOG4NET-232
> URL: https://issues.apache.org/jira/browse/LOG4NET-232
> Project: Log4net
> Issue Type: Improvement
> Affects Versions: 1.2.10
> Environment: Any
> Reporter: Aron Weiler
> Priority: Minor
>
> ReaderWriterLock should be replaced with ReaderWriterLockSlim according to
> Microsoft for performance and simplification reasons.
> MSDN:
> http://msdn.microsoft.com/en-us/library/system.threading.readerwriterlock.aspx
> The .NET Framework has two reader-writer locks, ReaderWriterLockSlim and
> ReaderWriterLock. ReaderWriterLockSlim is recommended for all new
> development. ReaderWriterLockSlim is similar to ReaderWriterLock, but it has
> simplified rules for recursion and for upgrading and downgrading lock state.
> ReaderWriterLockSlim avoids many cases of potential deadlock. In addition,
> the performance of ReaderWriterLockSlim is significantly better than
> ReaderWriterLock.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
