This group exists to support the use of the .NET Power Threading Library produced by Jeffrey Richter/Wintellect.
The Library, documentation, sample code, and license agreement can be downloaded from http://Wintellect.com/PowerThreading.aspx.
More information about the library's classes can be found via Jeffrey Richter's Concurrent Affairs column in MSDN magazine: http://msdn.microsoft.com/en-us/magazine/cc501041.aspx
A video demonstrating my AsyncEnumerator can be found here: http://blogs.msdn.com/charlie/archive/2008/12/03/jeff-richter-video-on-asynchronous-programming-and-his-power-threading-library.aspx
A Microsoft geekSpeak event demonstrating the Silverlight version of my AsyncEnumerator and its debug features can be found here: http://channel9.msdn.com/shows/geekSpeak/geekSpeak-recording-The-PowerThreading-Library-for-Silverlight-with-Jeffrey-Richter/.
Thank you very very much for detailed answer and sharing your knowledge and thoughts. I want to apologize for not providing enough details and my bad English
An exception is not a bad thing unless it is unhandled. Logging every exception thrown is like logging every method that returns false – there is no value to
Sorry, I forget one line in my cleanup code in previous post: if (InterlockedEx.IfThen(ref _disposed, 0, 1)) { Socket client = null; Interlocked.Exchange(ref
Thank you for answer. I do debug logging only so that's why I cant say if there are exception in BeginReceive. In production server it disabled almost fully.
You should NOT be logging exceptions. An unhandled exception terminates your app and the CLR logs the unhandled exception for you. So, YOU should not be doing